www.crunchydata.com/blog/crunchy...
www.crunchydata.com/blog/crunchy...
It wasn't just the designers focused on design it was everyone.
It wasn't just the designers focused on design it was everyone.
That's it.
That's it.
I mean why wouldn't you execute SQL to sign up for a database newsletter?
I mean why wouldn't you execute SQL to sign up for a database newsletter?
* 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...
* 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...
\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...
\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...
To me seemed a requirement for any production Iceberg usage, otherwise you wake up shocked in a few months.
To me seemed a requirement for any production Iceberg usage, otherwise you wake up shocked in a few months.
That's a new one, but will totally take it.
That's a new one, but will totally take it.
Further many of these tools often caused production outages.
We knew as soon as we launched Crunchy Data Warehouse we had to solve that.
Further many of these tools often caused production outages.
We knew as soon as we launched Crunchy Data Warehouse we had to solve that.
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.
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.
Speed up Postgres analytical queries 100x with 2 commands.
Speed up Postgres analytical queries 100x with 2 commands.
Now you can seamlessly move data and stream changes from your operational database into an analytical system.
www.crunchydata.com/blog/logical...
Now you can seamlessly move data and stream changes from your operational database into an analytical system.
www.crunchydata.com/blog/logical...
Now you can seamlessly move data and stream changes from your operational database into an analytical system.
www.crunchydata.com/blog/logical...
bsky.app/profile/crun...
Now you can seamlessly move data and stream changes from your operational database into an analytical system.
www.crunchydata.com/blog/logical...
bsky.app/profile/crun...
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
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