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?

🐘 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

What's this? Flexible/variable long term backup retention 👀

I've encountered a database without constraints that "enforces them within the app" I've encountered data quality issues. Postgres has a variety of constraints to help, not just primary/unique and foreign keys, but also not null and check constraints.

Something I've always found pride in is making developer tooling more accessible. You won't find many that think Postgres isn't powerful, but navigating it can be overwhelming. Scheduled jobs in a database aren't a "new thing", pg_cron has long been around but it wasn't always "friendly".

Partitioning in Postgres is great if you've got any form of time series data. It can allow higher ingest, faster queries, and easily archiving old data. Common examples could be:

- logs
- events
- metrics

A big part of building Crunchy Data Warehouse was ease of use. How easy is it to load data from existing public datasets?

Step 1: Point at your dataset and we'll load it for you
Step 2: Query it
Step 3: Profit

A while back we added a command palette to Crunchy Bridge (⌘ + K and get a set of shortcuts that you could easily navigate by typing). I personally love and use it all the time!

BUT, most of our users don't log in every day. So we exposed it directly in the nav to make it easy to find.

At movie theatre power went out, unsure if they’ll be able to play movie they make announcement about it.

Kid says can we start the movie back.

I ask if he was listening.

Apparently he meant this movie

CREATE TABLE measurements_staging (like measurements);

INSERT INTO measurements_staging VALUES ('Charleston', 21.3);

WITH new_rows as (
DELETE FROM measurements_staging returning *
) INSERT INTO measurements SELECT * FROM new_rows;