Craig

@craigkerstiens.com

Product @crunchydata previously MSFT/Citus/Heroku. Talk a lot about Postgres and startups. Why Postgres? https://www.crunchydata.com/why-postgres

We've got food duty at the first kids travel tournament of the year, was thinking about trying to pull off good quality pour over coffee. Anyone have good mechanisms when unclear a good power source for kettle exists?

Way back at Heroku when were having a company onsite... we took the entire company to the SF MOMA for a Dieter Rams exhibit. It wasn't just the designers focused on design it was everyone.

The details matter. In this case, completely revamping our newsletter signup screen ahead of an upcoming conference. I mean why wouldn't you execute SQL to sign up for a database newsletter?

New release of pg_parquet including: * Amazon S3 * Azure Blob Storage * Google Cloud Storage * http(s) stores * local files Still the easiest way to simplify some of your ETL allowing Postgres and parquet to play well together. www.crunchydata.com/blog/announc...

Announcing pg_parquet v.0.4.0: Google Cloud Storage, https storage, and more | Crunchy Data Blog

pg_parquet is a copy/to from for Postgres and Parquet. We're excited to announce integration with Google Cloud storage, https, and additional formats.

crunchydata.com

Updating my nulls today with: \pset null 🤖 Can't decide if it's for R2-D2, C-3PO, or BB-8, but closest I can get for May the 4th. May keep it for a few days...

My guess would be people are just using Iceberg connectors, see things seem to work, and compaction is an after-thought. That's why IMO good Iceberg support is not a connector feature but an engine feature. Like what Crunchy is doing with their DWH, or, for Kafka, Confluent with Tableflow.

A shocking take-away for me from a few weeks ago at Iceberg Summit and similarly at Data Council today is for all those using Iceberg yet so few doing compaction on their data lake files. To me seemed a requirement for any production Iceberg usage, otherwise you wake up shocked in a few months.

In talking with customers that were using CDC tools to get data from Postgres into a data warehouse, 80% of their spend on ETL was the Postgres data movement. Further many of these tools often caused production outages. We knew as soon as we launched Crunchy Data Warehouse we had to solve that.

@andypavlo.bsky.social on HN sums it up well OLAP vs. OLTP isn't right vs. wrong, they're designed for different things. Have a version of this on a slide when explaining Crunchy Data Warehouse and how it's for very different purposes than stock Postgres.

Bild

Today we're announcing the availability of logical replication from Postgres to Iceberg with Crunchy Data Warehouse. Now you can seamlessly move data and stream changes from your operational database into an analytical system. www.crunchydata.com/blog/logical...

Logical replication from Postgres to Iceberg | Crunchy Data Blog

We've launched native logical replication from Postgres tables in any Postgres server to Iceberg tables managed by Crunchy Data Warehouse.

crunchydata.com

🐘 meets 🧊 End to end, under 2 minutes. - Two commands to replicate data from Postgres -> Iceberg - Synced over 10m rows under a minute - Data is continually processed and updated in Iceberg - count(*) in Postgres over 300ms down to under 20ms