/explore

Click through on any links that interest you or select the planets on the right to continue exploring the Outer Web.
You are here

 sophiabits.com
Identifying slow PostgreSQL queries | Sophia Willows
| | e7e6.github.io
pg_stat_statements PGSQLPhriday - Anthony Nowocien
2.1 parsecs away

Travel
| | With Michael of pgMustard fame current host of #PGSQLPhriday, I could not resist revisiting this rather abondoned place of the interweb. As a short prelude, PGSQL Phriday is a blog event to talk of all things PostgreSQL and this week topic is about pg_stat_statements. pg_stat_statement is a module available since 2009 in Postgres 8.4. It tracks execution statistics on all SQL statements that have been executed. Since version 13, it also tracks planning statistics.
| | andyatkinson.com
PGSQL Phriday #008 - pg_stat_statements, PgHero, Query ID | Software Engineer, Author, High Performance PostgreSQL for Rails
1.5 parsecs away

Travel
| | I'm late to the party, but wanted to sneak in a PGSQL Phriday entry for this community blog post series.
| | jvns.ca
SQL queries don't start with SELECT
2.7 parsecs away

Travel
| | SQL queries don't start with SELECT
| | postgrespro.com
Queries in PostgreSQL: 4. Index scan : Postgres Professional
26.1 parsecs away

Travel
| In previous articles we discussed query execution stages and statistics . Last time, I started on data access methods, namely Sequential scan . Today we will cover Index Scan. This article requires a basic understanding of the index method interface. If words like "operator class" and "access method properties" don't ring a bell, check out my article on indexes from a while back for a refresher. Plain Index Scan Indexes return row version IDs (tuple IDs, or TIDs for short), which can be handled in one of...