Product

Planner statistics for indexed expressions

Summary: PostgreSQL is gathering statistics for indexed expressions, in order to make good choices of query plans.

Continue reading

Planner statistics in PostgreSQL

Summary: Planner statistics play a key role in improving the performance of the database. The query planner uses the statistical data to generate efficient run plans for queries. The purpose of this post is to explain the types of statistics in PostgreSQL and how to read and understand them.

Continue reading

pg_show_plans: Inspect execution plans of queries running in PostgreSQL

Summary: The pg_show_plans extension can show query plans of all the currently running SQL statements. Query plans can be shown in several formats, like JSON or YAML.

Continue reading

pg_store_plans: Track PostgreSQL execution plans for queries

Summary: The pg_store_plans module provides a means for tracking execution plan statistics of all SQL statements executed by a server.

Continue reading

pg_hint_plan: Details in hinting

Summary: in this article, let’s take a look at the detailed usage of pg_hint_plan in various scenarios.

Continue reading

pg_hint_plan: The hint table

Summary: The pg_hint_plan extension provides a hint table, through which you can change the execution plan of a query in a convenient way.

Continue reading

pg_hint_plan: Introduction

Summary: The pg_hint_plan extension gives PostgreSQL ability to manually force some decisions in execution plans.

Continue reading

pg_stat_kcache: Gather I/O and CPU statistics of queries

Summary: The pg_stat_kcache extension gathers statistics about physical disk access and CPU consumption done by backends.

Continue reading

pg_qualstats: PostgreSQL index advisor

Summary: The pg_qualstats extension gathers statistics about predicates, helping find what indices are missing.

Continue reading

hypopg: Hypothetical Indexes

Summary: A hypothetical, or virtual, index is an index that does not really exist, and therefore does not cost CPU, disk or any resource to create. They are useful to find out whether specific indexes can increase the performance for problematic queries, since you can discover if PostgreSQL will use these indexes or not without having to spend resources to create them.

Continue reading