PostgreSQL: ltree vs. WITH RECURSIVE
WITH RECURSIVE in PostgreSQL is efficient. However, ltree does have its strengths as well. Let us take a closer look. | Improve performance
SQL trickery: Hypothetical aggregates
“If we had this data what would it mean?” - read more about this PostgreSQL technique, what it is good for & how it works.
Composite type performance issues in PostgreSQL
Table functions & performance: Solve performance issues related to stored procedures and or a composite data type in PostgreSQL
PostgreSQL: Speeding up recursive queries and hierarchical data
How to use a hierarchical query, which is an SQL query that handles model data such as the structure of organizations - find out more
SQL trickery: Configuring window functions
How to use window functions and analytics - these have long been around in PostgreSQL and are widely used by advanced developers.
How to count hits on a website - concurrent counting in PostgreSQL
How to grant users access to a certain piece of data a limited number of times. What happens if two users access it concurrently?
PostgreSQL: Network latency does make a BIG difference
Find out about how network latency is essential to PostgreSQL database performance. Measure the performance impact caused by latency.
PostgreSQL: now() vs. 'NOW'::timestamp vs. clock_timestamp()
How to use the PostgreSQL: now() vs. 'NOW'::timestamp vs. clock_timestamp() | Issues with time and date in PostgreSQL database applications
Speeding up count(*): Why not use max(id) - min(id)
The usage of max(id) - min(id) to speed up count(*) may seem like a good approach when it comes to speeding up the process, but it can be problematic.
pg_show_plans: Watching execution plans in PostgreSQL LIVE
pg_show_plans is an extension developed by CYBERTEC, which shows all active query plans in PostgreSQL | Execution plan live in PostgreSQL
