Discussion of PostgreSQL's performance issues. Please see Guide to reporting problems and Slow Query Questions for some tips on how to write your performance question.
| Thread | Author | Time |
|---|---|---|
| Re: Terribly slow query with very good plan? | Vijaykumar Jain | 21:25 |
| Thread | Author | Time |
|---|---|---|
| Query choosing Bad Index Path | Valli Annamalai | 05:15 |
| Query choosing Bad Index Path | Valli Annamalai | 06:06 |
| Re: Query choosing Bad Index Path | Pavel Stehule | 06:18 |
| Re: Query choosing Bad Index Path | Julien Rouhaud | 06:18 |
| slow "select count(*) from information_schema.tables;" in some cases | Lars Aksel Opsahl | 16:56 |
| Re: slow "select count(*) from information_schema.tables;" in some cases | Justin Pryzby | 17:09 |
| Re: slow "select count(*) from information_schema.tables;" in some cases | Lars Aksel Opsahl | 17:39 |
| Re: slow "select count(*) from information_schema.tables;" in some cases | Vijaykumar Jain | 17:48 |
| Re: slow "select count(*) from information_schema.tables;" in some cases | Lars Aksel Opsahl | 18:55 |
| Re: slow "select count(*) from information_schema.tables;" in some cases | Tom Lane | 19:02 |
| Re: slow "select count(*) from information_schema.tables;" in some cases | Lars Aksel Opsahl | 19:11 |
| Re: slow "select count(*) from information_schema.tables;" in some cases | Imre Samu | 19:51 |
| Thread | Author | Time |
|---|---|---|
| Query choosing Bad Index Path (ASC/DESC ordering). | Valli Annamalai | 05:55 |
| Re: Query choosing Bad Index Path (ASC/DESC ordering). | Mind Body Nature | 12:04 |
| Re: slow "select count(*) from information_schema.tables;" in some cases | Lars Aksel Opsahl | 12:28 |
| Thread | Author | Time |
|---|---|---|
| Query chooses Bad Index Path | Valli Annamalai | 05:37 |
| Re: Query chooses Bad Index Path | Tomas Vondra | 16:51 |
| Thread | Author | Time |
|---|---|---|
| Re: Poor performance PostgreSQL 13/ PostGIS 3.x | Merlin Moncure | 15:38 |
| Thread | Author | Time |
|---|---|---|
| Slow Running Queries in Azure PostgreSQL 📎 | Kumar, Mukesh | 14:11 |
| Re: Slow Running Queries in Azure PostgreSQL | Justin Pryzby | 21:27 |
| Thread | Author | Time |
|---|---|---|
| RE: An I/O error occurred while sending to the backend (PG 13.4) | ldh@laurent-hasson.com | 00:47 |
| Re: An I/O error occurred while sending to the backend (PG 13.4) | Justin Pryzby | 01:04 |
| Re: An I/O error occurred while sending to the backend (PG 13.4) | Justin Pryzby | 02:00 |
| Slow plan choice with prepared query | Mark Saward | 03:37 |
| Re: An I/O error occurred while sending to the backend (PG 13.4) | Ranier Vilela | 11:50 |
| Re: An I/O error occurred while sending to the backend (PG 13.4) | Justin Pryzby | 12:59 |
| Re: An I/O error occurred while sending to the backend (PG 13.4) | Ranier Vilela | 13:46 |
| Advice needed: query performance deteriorates by 2000% within 1 minute | Peter Adlersburg | 13:53 |
| Re: Advice needed: query performance deteriorates by 2000% within 1 minute | Michael Lewis | 15:05 |
| Re: Advice needed: query performance deteriorates by 2000% within 1 minute | Tom Lane | 16:10 |
| Re: Slow plan choice with prepared query | MichaelDBA | 18:45 |
| Re: Slow plan choice with prepared query | MichaelDBA | 19:55 |
| Thread | Author | Time |
|---|---|---|
| RE: Slow Running Queries in Azure PostgreSQL | Kumar, Mukesh | 12:41 |
| Re: An I/O error occurred while sending to the backend (PG 13.4) | Justin Pryzby | 13:02 |
| slow query to improve performace 📎 | Ayub Khan | 20:18 |
| Re: slow query to improve performace | Justin Pryzby | 22:52 |
| Thread | Author | Time |
|---|---|---|
| Never Ending query in PostgreSQL 📎 | Kumar, Mukesh | 04:40 |
| Re: Never Ending query in PostgreSQL | Julien Rouhaud | 12:22 |
| Re: Never Ending query in PostgreSQL | Jeff Janes | 17:20 |
| Thread | Author | Time |
|---|---|---|
| Re: slow query to improve performace | Jeff Janes | 03:18 |
| RE: An I/O error occurred while sending to the backend (PG 13.4) | ldh@laurent-hasson.com | 16:50 |
| RE: An I/O error occurred while sending to the backend (PG 13.4) | ldh@laurent-hasson.com | 21:43 |
| Re: An I/O error occurred while sending to the backend (PG 13.4) | Justin Pryzby | 22:05 |
| RLS not using index scan but seq scan when condition gets a bit complicated | Charles Huang | 23:33 |