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: proposal: schema variables 📎 | Pavel Stehule | 08:17 |
| Thread | Author | Time |
|---|---|---|
| Re: proposal: schema variables 📎 | Pavel Stehule | 04:44 |
| Re: Request to help on Query improvement suggestion. | Marlene Villanueva | 17:15 |
| Thread | Author | Time |
|---|---|---|
| Sudden insert performance degradation | Henrique Montenegro | 14:23 |
| Re: Sudden insert performance degradation | Sebastian Dressler | 15:20 |
| Re: Sudden insert performance degradation | Michael Lewis | 16:27 |
| Re: Sudden insert performance degradation | Henrique Montenegro | 16:42 |
| Re: Sudden insert performance degradation | Henrique Montenegro | 16:48 |
| Re: Sudden insert performance degradation | Sebastian Dressler | 16:50 |
| Re: Sudden insert performance degradation | Henrique Montenegro | 17:02 |
| Thread | Author | Time |
|---|---|---|
| Re: Sudden insert performance degradation | Jeff Janes | 00:05 |
| Re: Sudden insert performance degradation | Henrique Montenegro | 01:02 |
| Re: Sudden insert performance degradation | Henrique Montenegro | 13:05 |
| Thread | Author | Time |
|---|---|---|
| Re: Sudden insert performance degradation 📎 | Henrique Montenegro | 01:13 |
| Re: Sudden insert performance degradation | Sebastian Dressler | 08:03 |
| Re: Sudden insert performance degradation | Henrique Montenegro | 12:24 |
| Re: Sudden insert performance degradation | Henrique Montenegro | 18:49 |
| Re: Sudden insert performance degradation | Justin Pryzby | 20:03 |
| Thread | Author | Time |
|---|---|---|
| Same query taking less time in low configuration machine 📎 | Vishwa Kalyankar | 15:43 |
| Re: Same query taking less time in low configuration machine | Justin Pryzby | 16:04 |
| Re: Same query taking less time in low configuration machine | Vishwa Kalyankar | 16:51 |
| Re: Same query taking less time in low configuration machine | Justin Pryzby | 17:03 |
| Thread | Author | Time |
|---|---|---|
| Re: Same query taking less time in low configuration machine | Vishwa Kalyankar | 07:59 |
| Thread | Author | Time |
|---|---|---|
| Too few rows expected by Planner on partitioned tables | Julian Wolf | 13:09 |
| Re: Too few rows expected by Planner on partitioned tables | Justin Pryzby | 17:27 |
| Thread | Author | Time |
|---|---|---|
| Re: Too few rows expected by Planner on partitioned tables | Julian Wolf | 06:33 |
| Re: Too few rows expected by Planner on partitioned tables | Justin Pryzby | 12:28 |
| Re: Too few rows expected by Planner on partitioned tables | Justin Pryzby | 14:40 |
| Thread | Author | Time |
|---|---|---|
| Re: Too few rows expected by Planner on partitioned tables | Julian Wolf | 06:17 |
| Problems with Multixacts LWLocks | Czarek | 14:18 |
| Thread | Author | Time |
|---|---|---|
| Hstore index for full text search | Burhan Akbulut | 20:52 |
| Re: Hstore index for full text search | Michael Lewis | 21:55 |
| Re: Hstore index for full text search | Tom Lane | 22:46 |
| Re: Hstore index for full text search | Michael Lewis | 22:57 |
| Re: Is there a known bug with SKIP LOCKED and "tuple to be locked was already moved to another partition due to concurrent update"? | Jim Jarvie | 22:58 |
| Re: Hstore index for full text search | Tom Lane | 23:30 |
| Thread | Author | Time |
|---|---|---|
| Query takes way longer with LIMIT, and EXPLAIN takes way longer than actual query | Ken Tanzer | 21:34 |
| Re: Query takes way longer with LIMIT, and EXPLAIN takes way longer than actual query | Justin Pryzby | 22:04 |
| Re: Query takes way longer with LIMIT, and EXPLAIN takes way longer than actual query | Ken Tanzer | 22:40 |
| Thread | Author | Time |
|---|---|---|
| Re: Query takes way longer with LIMIT, and EXPLAIN takes way longer than actual query | Jeff Janes | 00:24 |
| Re: Query takes way longer with LIMIT, and EXPLAIN takes way longer than actual query | Justin Pryzby | 00:55 |
| Thread | Author | Time |
|---|---|---|
| Replication lag due to lagging restart_lsn | Satyam Shekhar | 16:27 |
| CPU hogged by concurrent SELECT..FOR UPDATE SKIP LOCKED | Jim Jarvie | 23:52 |
| Thread | Author | Time |
|---|---|---|
| Re: CPU hogged by concurrent SELECT..FOR UPDATE SKIP LOCKED | Michael Lewis | 00:08 |
| Re: CPU hogged by concurrent SELECT..FOR UPDATE SKIP LOCKED | Jim Jarvie | 00:21 |
| Re: CPU hogged by concurrent SELECT..FOR UPDATE SKIP LOCKED | Henrique Montenegro | 00:38 |
| Re: CPU hogged by concurrent SELECT..FOR UPDATE SKIP LOCKED | Michael Lewis | 00:39 |
| Re: CPU hogged by concurrent SELECT..FOR UPDATE SKIP LOCKED | Michael Lewis | 00:45 |
| Re: CPU hogged by concurrent SELECT..FOR UPDATE SKIP LOCKED | Laurenz Albe | 06:04 |
| Re: Replication lag due to lagging restart_lsn | Kyotaro Horiguchi | 11:43 |
| Re: Replication lag due to lagging restart_lsn | Kiran Singh | 13:15 |
| Thread | Author | Time |
|---|---|---|
| Re: CPU hogged by concurrent SELECT..FOR UPDATE SKIP LOCKED | Jim Jarvie | 13:35 |
| Re: CPU hogged by concurrent SELECT..FOR UPDATE SKIP LOCKED | Michael Lewis | 17:30 |
| Re: CPU hogged by concurrent SELECT..FOR UPDATE SKIP LOCKED | Jim Jarvie | 21:13 |
| Re: CPU hogged by concurrent SELECT..FOR UPDATE SKIP LOCKED | Michael Lewis | 21:42 |
| Re: CPU hogged by concurrent SELECT..FOR UPDATE SKIP LOCKED | Jim Jarvie | 22:39 |
| Re: CPU hogged by concurrent SELECT..FOR UPDATE SKIP LOCKED | Michael Lewis | 23:01 |
| Re: CPU hogged by concurrent SELECT..FOR UPDATE SKIP LOCKED | David Rowley | 23:37 |
| Thread | Author | Time |
|---|---|---|
| Re: CPU hogged by concurrent SELECT..FOR UPDATE SKIP LOCKED | Thomas Munro | 04:34 |
| Re: CPU hogged by concurrent SELECT..FOR UPDATE SKIP LOCKED | Jim Jarvie | 15:24 |
| Thread | Author | Time |
|---|---|---|
| sizing / capacity planning tipps related to expected request or transactions per second | Dirk Krautschick | 16:39 |
| Re: sizing / capacity planning tipps related to expected request or transactions per second | MichaelDBA | 16:49 |
| Re: sizing / capacity planning tipps related to expected request or transactions per second | Pavel Stehule | 16:51 |
| Re: CPU hogged by concurrent SELECT..FOR UPDATE SKIP LOCKED | Jeff Janes | 17:58 |
| Thread | Author | Time |
|---|---|---|
| Re: Too few rows expected by Planner on partitioned tables | Julian Wolf | 06:54 |
| Re: Too few rows expected by Planner on partitioned tables | Michael Lewis | 13:32 |
| Thread | Author | Time |
|---|---|---|
| Query performance issue | Nagaraj Raj | 21:18 |
| Re: Query performance issue | Thomas Kellerer | 21:23 |
| Re: Query performance issue | Nagaraj Raj | 21:24 |
| Re: Query performance issue | Tomas Vondra | 21:36 |
| Re: Query performance issue | Michael Lewis | 21:39 |
| Re: Query performance issue | Michael Lewis | 21:41 |
| Re: Query performance issue | Nagaraj Raj | 21:44 |
| Re: Query performance issue | Michael Lewis | 21:55 |
| Re: Query performance issue | Nagaraj Raj | 22:20 |
| Thread | Author | Time |
|---|---|---|
| Re: Query performance issue | David Rowley | 08:16 |
| Re: Query performance issue | Michael Lewis | 13:42 |
| Re: Query performance issue | Nagaraj Raj | 21:49 |
| Thread | Author | Time |
|---|---|---|
| Re: CPU hogged by concurrent SELECT..FOR UPDATE SKIP LOCKED | Raj | 18:04 |
| Thread | Author | Time |
|---|---|---|
| AW: Query performance issue | Dirk Krautschick | 10:29 |
| Query Performance in bundled requests | Dirk Krautschick | 10:30 |
| Re: Query Performance in bundled requests | Justin Pryzby | 10:49 |
| AWS RDS PostgreSQL CPU Spiking to 100% | aditya desai | 13:33 |
| Re: AWS RDS PostgreSQL CPU Spiking to 100% | Pavel Stehule | 14:36 |
| Re: AWS RDS PostgreSQL CPU Spiking to 100% | Jeff Janes | 16:05 |
| Thread | Author | Time |
|---|---|---|
| Re: CPU hogged by concurrent SELECT..FOR UPDATE SKIP LOCKED | Jim Jarvie | 18:29 |
| Thread | Author | Time |
|---|---|---|
| Re: CPU hogged by concurrent SELECT..FOR UPDATE SKIP LOCKED | David Rowley | 13:52 |
| Re: CPU hogged by concurrent SELECT..FOR UPDATE SKIP LOCKED | Alvaro Herrera | 14:55 |
| Performance Issue (Not using Index when joining two tables). | Gopisetty, Ramesh | 14:58 |
| Re: Performance Issue (Not using Index when joining two tables). | Tomas Vondra | 16:47 |
| Re: Performance Issue (Not using Index when joining two tables). | Tom Lane | 17:07 |
| Thread | Author | Time |
|---|---|---|
| Re: Performance Issue (Not using Index when joining two tables). | Michael Lewis | 02:51 |
| Re: Performance Issue (Not using Index when joining two tables). | Gopisetty, Ramesh | 03:18 |
| Re: Performance Issue (Not using Index when joining two tables). | Tom Lane | 17:40 |
| autoanalyze creates bad plan, manual analyze fixes it? | Robert Treat | 23:11 |
| Re: autoanalyze creates bad plan, manual analyze fixes it? | Justin Pryzby | 23:41 |
| Thread | Author | Time |
|---|---|---|
| Re: autoanalyze creates bad plan, manual analyze fixes it? | Pavel Stehule | 04:53 |
| Re: autoanalyze creates bad plan, manual analyze fixes it? | Robert Treat | 05:21 |
| Single column vs composite partial index | Nagaraj Raj | 22:33 |
| Thread | Author | Time |
|---|---|---|
| Performance issue when we use policies for Row Level Security along with functions | Gopisetty, Ramesh | 03:39 |
| Re: Single column vs composite partial index | Justin Pryzby | 04:18 |
| Re: Single column vs composite partial index | Nagaraj Raj | 06:59 |
| Re: Performance issue when we use policies for Row Level Security along with functions | luis.roberto | 10:52 |
| Re: Performance issue when we use policies for Row Level Security along with functions | Tom Lane | 14:17 |
| Thread | Author | Time |
|---|---|---|
| Re: Single column vs composite partial index | Michael Lewis | 20:54 |
| Thread | Author | Time |
|---|---|---|
| Re: proposal: schema variables | Michael Paquier | 03:56 |
| Re: proposal: schema variables | Pavel Stehule | 03:58 |
| Re: proposal: schema variables 📎 | Pavel Stehule | 18:49 |
| Thread | Author | Time |
|---|---|---|
| How to encrypt database password in pgpass or unix file to run batch jobs through shell script | aditya desai | 09:34 |
| Re: How to encrypt database password in pgpass or unix file to run batch jobs through shell script | Bruce Momjian | 19:51 |
| Thread | Author | Time |
|---|---|---|
| Re: AWS RDS PostgreSQL CPU Spiking to 100% | aditya desai | 15:51 |
| Re: AWS RDS PostgreSQL CPU Spiking to 100% | Prince Pathria | 16:09 |
| Is it possible to specify minimum number of rows planner should consider? | Timothy Garnett | 20:12 |
| Re: Is it possible to specify minimum number of rows planner should consider? | Tom Lane | 21:06 |
| Re: Is it possible to specify minimum number of rows planner should consider? | Matthew Bellew | 21:45 |
| Thread | Author | Time |
|---|---|---|
| Re: Is it possible to specify minimum number of rows planner should consider? | Timothy Garnett | 00:22 |
| Thread | Author | Time |
|---|---|---|
| Re: AWS RDS PostgreSQL CPU Spiking to 100% | aditya desai | 07:13 |
| SSL connection getting rejected on AWS RDS | aditya desai | 07:19 |
| Re: SSL connection getting rejected on AWS RDS | Hannah Huang | 11:17 |
| Re: SSL connection getting rejected on AWS RDS | aditya desai | 15:50 |
| Thread | Author | Time |
|---|---|---|
| Re: proposal: schema variables | Michael Paquier | 03:38 |
| Re: SSL connection getting rejected on AWS RDS | Hannah Huang | 04:51 |
| Re: proposal: schema variables 📎 | Pavel Stehule | 05:08 |
| Thread | Author | Time |
|---|---|---|
| Too many waits on extension of relation | avinash varma | 05:02 |
| Re: Too many waits on extension of relation | Michael Lewis | 16:44 |
| Re: Too many waits on extension of relation | avinash varma | 17:06 |
| Re: Too many waits on extension of relation | Sushant Pawar | 17:38 |
| Re: Too many waits on extension of relation | MichaelDBA | 18:03 |
| Thread | Author | Time |
|---|---|---|
| Re: Too many waits on extension of relation | Laurenz Albe | 03:37 |
| Re: Too many waits on extension of relation | avinash varma | 03:59 |
| Thread | Author | Time |
|---|---|---|
| Indexing an XMLTABLE query? | Kanninen Anssi EXT | 05:39 |
| Re: Indexing an XMLTABLE query? | Pavel Stehule | 05:59 |
| Thread | Author | Time |
|---|---|---|
| Re: Performance issue when we use policies for Row Level Security along with functions | Gopisetty, Ramesh | 06:46 |
| Performance issue when we use policies for Row Level Security along with functions | David G. Johnston | 07:26 |
| Thread | Author | Time |
|---|---|---|
| Slow Query | Parth Shah | 17:30 |
| Re: Slow Query | Michael Lewis | 19:17 |
| Thread | Author | Time |
|---|---|---|
| Re: Slow Query 📎 | Parth Shah | 01:11 |
| Re: Slow Query | Michael Lewis | 04:51 |
| Poor Performance running Django unit tests after upgrading from 10.6 | Roger Hunwicks | 05:21 |
| Re: Poor Performance running Django unit tests after upgrading from 10.6 | Laurenz Albe | 06:56 |
| Re: Poor Performance running Django unit tests after upgrading from 10.6 | Andrew Dunstan | 10:59 |
| Re: Poor Performance running Django unit tests after upgrading from 10.6 | Tom Lane | 13:56 |
| CPU Consuming query. Sequential scan despite indexing. | aditya desai | 15:04 |
| Re: CPU Consuming query. Sequential scan despite indexing. | Michael Lewis | 16:26 |
| Thread | Author | Time |
|---|---|---|
| Re: CPU Consuming query. Sequential scan despite indexing. | Laurenz Albe | 08:36 |
| Thread | Author | Time |
|---|---|---|
| Re: CPU Consuming query. Sequential scan despite indexing. | Michael Lewis | 16:20 |
| Thread | Author | Time |
|---|---|---|
| Re: Query Performance / Planner estimate off | Sebastian Dressler | 12:38 |
| Re: Query Performance / Planner estimate off | Mats Olsen | 14:42 |
| Re: Query Performance / Planner estimate off | Michael Lewis | 15:29 |
| Re: Query Performance / Planner estimate off | Sebastian Dressler | 15:35 |
| Thread | Author | Time |
|---|---|---|
| Query performance | Nagaraj Raj | 00:32 |
| Re: Query performance | Justin Pryzby | 01:09 |
| Re: Query performance | David G. Johnston | 01:11 |
| Re: CPU Consuming query. Sequential scan despite indexing. | aditya desai | 05:21 |
| Re: CPU Consuming query. Sequential scan despite indexing. | aditya desai | 05:27 |
| Re: CPU Consuming query. Sequential scan despite indexing. | David G. Johnston | 05:32 |
| Re: CPU Consuming query. Sequential scan despite indexing. | aditya desai | 05:36 |
| Re: Query Performance / Planner estimate off | Mats Olsen | 06:21 |
| Re: Query Performance / Planner estimate off | Justin Pryzby | 06:37 |
| Re: Query Performance / Planner estimate off | Mats Olsen | 07:36 |
| Re: Query Performance / Planner estimate off | Justin Pryzby | 13:48 |
| Thread | Author | Time |
|---|---|---|
| Re: Query Performance / Planner estimate off | Mats Olsen | 12:16 |
| Thread | Author | Time |
|---|---|---|
| Profiling tool for postgresql queries | Debajyoti Datta | 22:33 |
| Thread | Author | Time |
|---|---|---|
| Postgres Optimizer ignores information about foreign key relationship, severly misestimating number of returned rows in join | Ehrenreich, Sigrid | 15:58 |
| Understanding bad estimate (related to FKs?) | Philip Semanchuk | 16:50 |
| Re: Understanding bad estimate (related to FKs?) | Justin Pryzby | 17:04 |
| Re: Understanding bad estimate (related to FKs?) | Philip Semanchuk | 17:14 |
| Re: Understanding bad estimate (related to FKs?) | Michael Lewis | 17:20 |
| Re: Understanding bad estimate (related to FKs?) | Philip Semanchuk | 18:55 |
| Re: Postgres Optimizer ignores information about foreign key relationship, severely misestimating number of returned rows in join | Justin Pryzby | 20:34 |
| Re: Postgres Optimizer ignores information about foreign key relationship, severly misestimating number of returned rows in join | David Rowley | 22:25 |
| Re: Postgres Optimizer ignores information about foreign key relationship, severly misestimating number of returned rows in join | Tom Lane | 22:54 |
| Thread | Author | Time |
|---|---|---|
| RE: Postgres Optimizer ignores information about foreign key relationship, severly misestimating number of returned rows in join | Ehrenreich, Sigrid | 07:50 |
| Thread | Author | Time |
|---|---|---|
| Re: Query Performance / Planner estimate off | Mats Olsen | 06:45 |
| Re: Postgres Optimizer ignores information about foreign key relationship, severly misestimating number of returned rows in join | Tom Lane | 16:55 |
| query plan using partial index expects a much larger number of rows than is possible | Olivier Poquet | 22:46 |
| Re: query plan using partial index expects a much larger number of rows than is possible | Tom Lane | 23:30 |
| Thread | Author | Time |
|---|---|---|
| Re: query plan using partial index expects a much larger number of rows than is possible | Olivier Poquet | 00:53 |
| Re: Understanding bad estimate (related to FKs?) | Justin Pryzby | 01:13 |
| RE: Postgres Optimizer ignores information about foreign key relationship, severly misestimating number of returned rows in join | Ehrenreich, Sigrid | 06:31 |
| Re: Postgres Optimizer ignores information about foreign key relationship, severly misestimating number of returned rows in join | Magnus Hagander | 09:57 |