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 | 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 |
RE: Postgres Optimizer ignores information about foreign key relationship, severly misestimating number of returned rows in join | Ehrenreich, Sigrid | 12:12 |
Re: query plan using partial index expects a much larger number of rows than is possible | Michael Lewis | 15:08 |
Re: Understanding bad estimate (related to FKs?) | Philip Semanchuk | 15:25 |
Re: Understanding bad estimate (related to FKs?) | Tomas Vondra | 22:48 |
Thread | Author | Time |
---|---|---|
Re: Understanding bad estimate (related to FKs?) | Philip Semanchuk | 14:56 |
Thread | Author | Time |
---|---|---|
Re: Understanding bad estimate (related to FKs?) | Guillaume Lelarge | 13:53 |