Are triggers really that slow in Postgres?
PostgreSQL trigger performance. Should we use tiggers at all? Find out how triggers perform in performance tests.
Window function: Why first_value and last_value are not bugs
PostgreSQL can be used for more than just trivial queries. A look into what a window function does: first_value and last_value in PostgreSQL.
PostgreSQL: Speeding up analytics and window functions
How to improve speed is by rearranging window functions in a clever way: some clever optimization can give you better database performance.
New features for sequences: gains and pitfalls
by
Laurenz Albe |
02.2018About sequences Sequences are used to generate artificial numeric primary key columns for tables. A sequence provides a “new ID” […]
Avoiding unnecessary function calls in PostgreSQL
Fix bad performance related to slow function calls: When it comes to slow procedures, PostgreSQL often isn't to blame. Here's why.
Searching for the best compromise: “Skyline” queries
What about making more intelligent queries in PostgreSQL? Skyline queries could be the answer for you. We show you how to set them up.
pg_crash: Making database crashes great again
pg_crash is the ultimate tool to stress test your PostgreSQL database and infrastructure as well as your high-availability infrastructure.
Distributed aggregates / aggregate pushdown in PostgreSQL
A feature from PostgreSQL 10 is related to Foreign Data Wrappers and is generally known as “aggregate pushdown”. Have a look!|
Writing your own aggregation functions
Database engines usually provide basic aggregate functions. This shows how to create your own code to calculate on the server side.
Trying out Postgres Bloom indexes
Let's set up a simple demo to exemplify “fields of application” for Bloom and to also gauge pros/cons/performance in comparison to B-tree.
