We just released a new version of Crunchy Postgres. Packed with security, access management, and monitoring updates. Giving you more flexibility and options for running production Postgres.
What happens when you query Postgres? Data can actually come from many different places like the application cache, buffer cache, and even down into the physical disk cache. This post surveys the data storage and flow of Postgres data.
When it comes to database performance, many think they are solving technical problems, but are solving a money problem. There are 2 phases to database-cost management, and understanding which phase you are in will help you understand your options for growth.
Crunchy Data is excited to release a new open source tool, Exporter2Perfdata. This connects Prometheus Exporters with Icinga2/Nagios. This also allows pgMonitor users to connect monitoring information from Prometheus to Icinga2 and Nagios.
David optimizes a slow query by splitting up a left join into two calls and using UNION ALL to combine them. The proof is in the pudding.
Which of my applications ran this SQL statement? Use SQL comments to track which application ran which queries.
For developers, databases are basically magic. Like Penn & Teller, this blog post is set to break the illusion. Databases are just like any other code, they have algorithms and processes. These algorithms and processes are meant to improve performance, but can cause limitations if they are not expected.
Craig's year end wrap-up of 5 things you can do for a healthier Postgres database next year.
If you have insert-only tables in a version of PostgreSQL earlier that 13, you could benefit from running a regularly scheduled VACUUM.
Almost a decade after range types were introduced, Postgres 14 makes it easier to write "boring SQL" for range data. Meet the "multirange" data type.