Crunchy Data

@crunchydata.com

Just Postgres www.crunchydata.com

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

How long has it been since you checked your cache hit ratio? Ideally most of your frequently queried data is in the buffer cache. We recommend 98-99% in the cache for transactional workloads - analytical workloads are lower.

Postgres does a good job of keeping internal statistics of your which are used to plan how queries are executed. But Postgres doesn't always know how columns are related. In this deep dive we look at hacking the statistics for improved performance

Hacking the Postgres Statistics Tables for Faster Queries | Crunchy Data Blog

Adding extended statistics can add information about how columns are related. Louise has some real life example queries and tips for working with extended table stats that can dramatically improve…

crunchydata.com

We all love pg_stat_statements but that data collects forever and can get a little stale. When should you reset it? Here are some tips from our support team.

Excited to announce built-in maintenance for Iceberg via Postgres. Now within Crunchy Data Warehouse we will automatically vacuum and continuously optimize your Iceberg data by compacting and cleaning up files. Dig into the details of how this works www.crunchydata.com/blog/automat...

Automatic Iceberg Maintenance Within Postgres | Crunchy Data Blog

Iceberg can create orphan files during snapshot changes or transaction rollbacks. Crunchy Data Warehouse automatically cleans up the orphan files using a new autovacuum feature.

crunchydata.com

SQL output can be messy. Psql options for formatting output. A handy option is \pset border 2 This will add top and bottom borders with double lines (╔, ╚, ╤, ╧, etc.). A Header row bordered with a double-line separator . Each row is separated by single lines. Each column is clearly separated.

Bild

Great to see this ability for "creating processing pipelines for append-only streams of data...We believe it is a foundational building block for building IoT applications on PostgreSQL that should be available to everyone, similar to pg_cron, pg_parquet, and pg_partman."

Crunchy Data@crunchydata.com · 2y ago

We’re excited to release pg_incremental today - a new extension for automated incremental updates. pg_incremental is like a supercharged pg_cron that runs data pipelines, data syncs, rollups, imports and exports. www.crunchydata.com/blog/pg_incr...

There are many incremental processing solutions, but they seem to never quite do what I need. I decided to build an extension that just keeps running the same command in Postgres with different parameters to do fast, reliable incremental data processing. That's pg_incremental. 1/n

Crunchy Data@crunchydata.com · 2y ago

We’re excited to release pg_incremental today - a new extension for automated incremental updates. pg_incremental is like a supercharged pg_cron that runs data pipelines, data syncs, rollups, imports and exports. www.crunchydata.com/blog/pg_incr...

Many big Postgres databases today use partitioning. Do you have a default partition? If not, you probably should. Default partitions are super important because they let you catch inconsistent data or bugs in your application code. www.crunchydata.com/blog/postgre...

Postgres Partitioning with a Default Partition | Crunchy Data Blog

Keith discusses the importance of having a default partition, how to monitor the default, and how to move rows to new child tables.

crunchydata.com

Know which queries consume the most time against your Postgres database? Pg_stat_statements will tell you if you don't already know: SELECT total_exec_time, mean_exec_time as avg_ms, calls, query FROM pg_stat_statements ORDER BY mean_exec_time DESC LIMIT 10; #dataBS

When working with psql in Postgres you can edit queries using \e \e will open your default editor thats been defined with $EDITOR What's your $EDITOR set to?