Not sure if I have this right but this is how I understand it
> So is the magic here that it's Postgres? What makes being able to query something in Postgres special?
There are a bunch of pros and cons to using Postgres vs. DuckDB. The basic difference is OLTP vs. OLAP. It seems pg_lake aims to give you the best of both. You can combine analytics queries with transactional queries.
pg_lake also stores and manages the Iceberg catalog. If you use DuckDB you'll need to have an external catalog to get the same guarantees.
I think if you're someone who was happy using Postgres, but had to explore alternatives like DuckDB because Postgres couldn't meet your OLAP needs, a solution like pg_lake would make your life a lot simpler. Instead of deploying a whole new OLAP system, you basically just install this extension and create the tables you want OLAP performance from with `create table ... using iceberg`
> when we say it’s now queryable by Postgres, does this mean that it takes that data and stores it in your PG db?
Postgres basically stores pointers to the data in S3. These pointers are in the Iceberg catalog that pg_lake manages. The tables managed by pg_lake are special tables defined with `create table ... using iceberg` which stores the data in Iceberg/Parquet files on S3 and executes queries partially with the DuckDB engine and partially with the Postgres engine.
It looks like there is good support for copying between the Iceberg/DuckDB/Parquet world and the traditional Postgres world.
> Or it remains in S3 and this is a translation layer for querying with PG?
Yes I think that's right -- things stay in S3 and there is a translation layer so Postgres can use DuckDB to interact with the Iceberg tables on S3. If you're updating a table created with `create table ... using iceberg`, I think all the data remains in S3 and is stored in Parquet files, safely/transactionally managed via the Iceberg format.
and don't forget that Grok is powered by illegal cancer-causing methane gas turbines in a predominantly black neighborhood of Memphis that already had poor air quality to begin with
There are a lot of myths about the way humans used to be, especially Native Americans. Were they utopian nature-lovers? Were they barbaric human-sacrificers?
A good book on this topic is The Dawn of Everything, written by an anthropologist and an archaeologist. A YouTube video from one of the authors is here https://www.youtube.com/watch?v=8SJi0sHrEI4
I disagree with the idea that "barbarism was common" in Native American societies. I don't think you can generalize from the Incas so directly like this
I've had a similar experience with Bluesky, though it's much more like Twitter than Hacker News. You can curate a good feed by following a ton of people, then unfollow the noisy ones as you look over the feed. You can use "starter packs" and hashtags to help get started, too.
Once you've found some people you like, this tool is somewhat helpful for finding more people you might like to follow:
I don't think the "noble savage" idea applies in this case. The problem of the noble savage idea is that it portrays indigenous people as simple, pure, and uncorrupted, while overlooking that indigenous people are complex just like non-indigenous people.
It's no myth that the Haudenosaunee and other indigenous people had sophisticated governments that could have inspired the writers of the US Constitution. The Haudenosaunee's democracy-ish form of government extends back probably a thousand years. The people who wrote the US Constitution had contact with these people. The exact extent to which this shaped the Constitution is up for debate, of course.
Yes, the US government draws from European roots too. I hope my kids learn about both the Magna Carta and the Great Law of Peace.
> So is the magic here that it's Postgres? What makes being able to query something in Postgres special?
There are a bunch of pros and cons to using Postgres vs. DuckDB. The basic difference is OLTP vs. OLAP. It seems pg_lake aims to give you the best of both. You can combine analytics queries with transactional queries.
pg_lake also stores and manages the Iceberg catalog. If you use DuckDB you'll need to have an external catalog to get the same guarantees.
I think if you're someone who was happy using Postgres, but had to explore alternatives like DuckDB because Postgres couldn't meet your OLAP needs, a solution like pg_lake would make your life a lot simpler. Instead of deploying a whole new OLAP system, you basically just install this extension and create the tables you want OLAP performance from with `create table ... using iceberg`
> when we say it’s now queryable by Postgres, does this mean that it takes that data and stores it in your PG db?
Postgres basically stores pointers to the data in S3. These pointers are in the Iceberg catalog that pg_lake manages. The tables managed by pg_lake are special tables defined with `create table ... using iceberg` which stores the data in Iceberg/Parquet files on S3 and executes queries partially with the DuckDB engine and partially with the Postgres engine.
It looks like there is good support for copying between the Iceberg/DuckDB/Parquet world and the traditional Postgres world.
> Or it remains in S3 and this is a translation layer for querying with PG?
Yes I think that's right -- things stay in S3 and there is a translation layer so Postgres can use DuckDB to interact with the Iceberg tables on S3. If you're updating a table created with `create table ... using iceberg`, I think all the data remains in S3 and is stored in Parquet files, safely/transactionally managed via the Iceberg format.
https://github.com/Snowflake-Labs/pg_lake/blob/main/docs/ice...