Earlier this week a VC friend was doing due diligence on a company. The conversation detoured to some things Crunchy Data and walked them through quickly the architecture of Crunchy Data Warehouse. Their draw literally dropped. Quotes from them: "Are customers pounding down

Replacing dbt? 🤔 Challenge accepted. pg_incremental is the first piece. A lot more in the pipeline.

We're excited to be a part of DuckDB DuckCon #6 this week in Amsterdam. Craig Kerstiens and Marco Slot are looking forward to learning more about DuckDB and the community. Craig and Marco are also ready to talk about the latest research and development when using Postgres with

how do you know someone uses too much psql? there are signs.

Today I got to play around with our new data warehouse product. - connected to the entire world's building footprint data in Overture Maps Foundation - made a local table of tornado path data from FEMA - joined them together - set up a web browser to view the join with pg_tileserv 💥

I've been pursuing the idea of using object storage as a shared fabric between Postgres servers for a while, and things are starting to look really smooth. Here is an example of exporting data to S3 using pg_parquet and then loading it into Iceberg using Crunchy Data Warehouse.

Using Cloud Rasters with PostGIS: With the postgis_raster extension, it is possible to access gigabytes of raster data from the cloud, without ever downloading the data. Rasters for PostGIS can be stored inside the database, or outside the database, on a local file system or

The things you can do with PostGIS are pretty incredible.

#Apache #Iceberg users, did you know with Crunchy Data Warehouse you get: - Built-in Iceberg catalog—no extra setup - S3 storage handled automatically Just run: ` CREATE TABLE my_table (id SERIAL, value TEXT) USING iceberg;` …and you’re good to go. No configurations. Just #SQL

Marco Slot (Marco Slot) put together code examples for using some of our favorite new tools for data pipelines - pg_parquet, pg_incremental, and pg_cron on the blog today. This is a simple, efficient, and cost effective end-to-end data pipeline: 1 - Archive off data

PostgreSQL extensions often have powerful synergies. By combining pg_parquet and pg_incremental you can build sophisticated incremental data pipelines.

Simple, efficient, and cost effective end-to-end data pipeline: 1 - Archive off data incrementally with a lightweight transactional ETL 2 - Store historical data in Parquet or Iceberg 3 - Query historical data with Crunchy Data Warehouse crunchydata.com/blog/increment…

Huge shout out to Crunchy Data for absolutely amazing support!

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. crunchydata.com/blog/logical-r…

Crunchy Data Marco Slot on "Convering database architectures in PostgreSQL and DuckDB" youtu.be/HZArjlMB6W4?fe…

Just announced: Snowflake has agreed to acquire Crunchy Data, bringing open-source Postgres tech into the AI Data Cloud. With this news, we will be introducing Snowflake Postgres: enterprise-grade, AI-ready, and fully managed. Run your most critical, AI-powered apps on

1/12. I'm excited to share our latest technical blog post on ParadeDB. After a brief hiatus focused on transforming ParadeDB into an enterprise-ready database, expect to hear a lot more from us. Today's post: How ParadeDB built an LSM on top of Postgres block storage. 🧵

.Abigale Kim (@abigalekim.bsky.social)'s paper is unleashed! It's the most complete eval of DB extensions/plugins. We analyze PostgreSQL, MySQL, MariaDB , SQLite, DuckDB, Redis S. TLDR: Postgres ecosystem is fraught w/ footguns. Other DBMSs have fewer extns but less problems. DuckDB has cleanest API.

No system hits the sweet spot of allowing for extensibility while maintaining systems safety. It would be nice if there was a standard plugin API (think POSIX) that allows compatibility across systems. Thanks to Marco Slot + David Andersen for their collaboration on this project