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 |
|---|---|---|
| distinguish index cost component from table component | Justin Pryzby | 14:14 |
| Re: distinguish index cost component from table component | Jeff Janes | 14:33 |
| Re: distinguish index cost component from table component 📎 | Justin Pryzby | 16:03 |
| Thread | Author | Time |
|---|---|---|
| allow disabling indexscans without disabling bitmapscans 📎 | Justin Pryzby | 16:50 |
| Re: allow disabling indexscans without disabling bitmapscans | Justin Pryzby | 19:34 |
| Thread | Author | Time |
|---|---|---|
| doc: alter table references bogus table-specific planner parameters 📎 | Justin Pryzby | 02:56 |
| Re: doc: alter table references bogus table-specific planner parameters | Simon Riggs | 03:48 |
| Re: doc: alter table references bogus table-specific planner parameters | Justin Pryzby | 04:13 |
| Re: doc: alter table references bogus table-specific planner parameters | Simon Riggs | 04:33 |
| Thread | Author | Time |
|---|---|---|
| Bad query plan when you add many OR conditions | Marco Colli | 01:11 |
| Re: Bad query plan when you add many OR conditions | Justin Pryzby | 03:06 |
| Re: Bad query plan when you add many OR conditions | Marco Colli | 11:03 |
| Re: Bad query plan when you add many OR conditions | Marco Colli | 13:30 |
| Re: Bad query plan when you add many OR conditions | Justin Pryzby | 13:34 |
| Re: Bad query plan when you add many OR conditions | Marco Colli | 14:53 |
| Re: Bad query plan when you add many OR conditions | Tom Lane | 15:18 |
| Re: Bad query plan when you add many OR conditions | Marco Colli | 16:03 |
| Re: Bad query plan when you add many OR conditions | Jeff Janes | 17:12 |
| Thread | Author | Time |
|---|---|---|
| Seeking reason behind performance gain in 12 with HashAggregate | Shira Bezalel | 16:29 |
| Re: Seeking reason behind performance gain in 12 with HashAggregate | Justin Pryzby | 16:42 |
| Re: Seeking reason behind performance gain in 12 with HashAggregate | Shira Bezalel | 17:34 |
| Re: Seeking reason behind performance gain in 12 with HashAggregate | Michael Lewis | 18:07 |
| Re: Seeking reason behind performance gain in 12 with HashAggregate | Shira Bezalel | 20:44 |
| Re: Seeking reason behind performance gain in 12 with HashAggregate | Tomas Vondra | 21:11 |
| Re: Seeking reason behind performance gain in 12 with HashAggregate | Shira Bezalel | 21:45 |
| Re: Bad query plan when you add many OR conditions | Tomas Vondra | 22:14 |
| Re: Seeking reason behind performance gain in 12 with HashAggregate | Alvaro Herrera | 22:15 |
| Thread | Author | Time |
|---|---|---|
| Re: Seeking reason behind performance gain in 12 with HashAggregate | Shira Bezalel | 00:11 |
| Re: Bad query plan when you add many OR conditions | Thomas Kellerer | 08:01 |
| shared buffers and startup process | Joao Junior | 15:29 |
| Thread | Author | Time |
|---|---|---|
| Re: shared buffers and startup process | Michael Paquier | 02:48 |
| Thread | Author | Time |
|---|---|---|
| Re: proposal: schema variables 📎 | Pavel Stehule | 21:10 |
| Thread | Author | Time |
|---|---|---|
| Re: proposal: schema variables | Tomas Vondra | 23:41 |
| Thread | Author | Time |
|---|---|---|
| Re: proposal: schema variables 📎 | Pavel Stehule | 05:08 |
| Thread | Author | Time |
|---|---|---|
| Re: proposal: schema variables 📎 | Pavel Stehule | 17:26 |
| Thread | Author | Time |
|---|---|---|
| Query optimization advice for beginners | Kemal Ortanca | 13:15 |
| Re: Query optimization advice for beginners | Andreas Kretschmer | 13:57 |
| Re: Query optimization advice for beginners | Kemal Ortanca | 15:33 |
| Re: Query optimization advice for beginners | Michael Lewis | 16:46 |
| Thread | Author | Time |
|---|---|---|
| Re: Query optimization advice for beginners | Laurenz Albe | 08:37 |
| Thread | Author | Time |
|---|---|---|
| Re: Specific query taking time to process | Fahiz Mohamed | 09:44 |
| Re: Specific query taking time to process | Duncan Whitham | 12:22 |
| Re: Specific query taking time to process | Tom Lane | 16:35 |
| Thread | Author | Time |
|---|---|---|
| Re: Specific query taking time to process | Duncan Whitham | 11:01 |
| Thread | Author | Time |
|---|---|---|
| Statistics on array values | Marco Colli | 14:18 |
| Re: Statistics on array values | Justin Pryzby | 14:23 |
| Re: Statistics on array values | Marco Colli | 14:38 |
| Re: Statistics on array values | Tom Lane | 17:11 |
| Re: Statistics on array values | Marco Colli | 18:26 |
| Re: Statistics on array values | Tom Lane | 18:32 |
| Re: Statistics on array values | Marco Colli | 18:55 |
| Thread | Author | Time |
|---|---|---|
| Slow performance with trivial self-joins | Benny Kramek | 20:38 |
| Re: Slow performance with trivial self-joins | Tom Lane | 21:10 |
| Thread | Author | Time |
|---|---|---|
| Writing 1100 rows per second | Arya F | 17:03 |
| Re: Writing 1100 rows per second | Laurenz Albe | 17:12 |
| Re: Writing 1100 rows per second | Justin Pryzby | 17:15 |
| Re: Writing 1100 rows per second | Arya F | 17:25 |
| Re: Writing 1100 rows per second | Haroldo Kerry | 17:46 |
| Re: Slow performance with trivial self-joins | Benny Kramek | 21:55 |
| Re: Slow performance with trivial self-joins | Adam Brusselback | 22:12 |
| Re: Slow performance with trivial self-joins | David Rowley | 23:47 |
| Thread | Author | Time |
|---|---|---|
| Re: Writing 1100 rows per second | Ogden Brash | 18:15 |
| Thread | Author | Time |
|---|---|---|
| TOAST table performance problem | Asya Nevra Buyuksoy | 13:07 |
| Sv: TOAST table performance problem | Andreas Joseph Krogh | 13:12 |
| Re: TOAST table performance problem 📎 | Asya Nevra Buyuksoy | 13:23 |
| Re: TOAST table performance problem | Asya Nevra Buyuksoy | 13:34 |
| Re: TOAST table performance problem | Andreas Joseph Krogh | 13:41 |
| Re: TOAST table performance problem | MichaelDBA | 13:52 |
| Re: TOAST table performance problem | Asya Nevra Buyuksoy | 14:16 |
| Re: TOAST table performance problem | Andreas Joseph Krogh | 14:19 |
| Re: TOAST table performance problem | Andreas Joseph Krogh | 14:42 |
| Re: TOAST table performance problem | Asya Nevra Buyuksoy | 14:59 |
| Re: TOAST table performance problem | Andreas Joseph Krogh | 15:15 |
| Re: proposal: schema variables 📎 | Pavel Stehule | 16:09 |
| Thread | Author | Time |
|---|---|---|
| Re: Writing 1100 rows per second | Jeff Janes | 19:30 |
| Thread | Author | Time |
|---|---|---|
| Fwd: TOAST table performance problem | Asya Nevra Buyuksoy | 07:52 |
| Bad selectivity estimate when using a sub query to determine WHERE condition | Chris Borckholder | 10:34 |
| Re: Fwd: TOAST table performance problem | Luís Roberto Weck | 12:31 |
| Re: Fwd: TOAST table performance problem | Asya Nevra Buyuksoy | 12:38 |
| Re: Fwd: TOAST table performance problem | Jeff Janes | 12:53 |
| Re: Fwd: TOAST table performance problem | Asya Nevra Buyuksoy | 12:59 |
| Re: Bad selectivity estimate when using a sub query to determine WHERE condition | Tom Lane | 15:39 |
| Re: proposal: schema variables 📎 | Pavel Stehule | 18:47 |
| Re: Bad selectivity estimate when using a sub query to determine WHERE condition | Justin Pryzby | 19:13 |
| Thread | Author | Time |
|---|---|---|
| Re: Writing 1100 rows per second | Amol Tarte | 05:28 |
| Re: Bad selectivity estimate when using a sub query to determine WHERE condition | Chris Borckholder | 08:09 |
| Re: Bad selectivity estimate when using a sub query to determine WHERE condition | Chris Borckholder | 08:12 |
| Thread | Author | Time |
|---|---|---|
| How to avoid UPDATE performance degradation in a transaction | Karl Düüna | 10:21 |
| Re: How to avoid UPDATE performance degradation in a transaction | David G. Johnston | 20:50 |
| Re: How to avoid UPDATE performance degradation in a transaction | Tom Lane | 21:16 |
| Thread | Author | Time |
|---|---|---|
| Re: How to avoid UPDATE performance degradation in a transaction | Karl Düüna | 07:14 |
| Re: How to avoid UPDATE performance degradation in a transaction | Michael Lewis | 17:54 |
| Thread | Author | Time |
|---|---|---|
| Re: proposal: schema variables 📎 | Pavel Stehule | 08:05 |
| Partial index creation always scans the entire table | MingJu Wu | 11:04 |
| Re: Partial index creation always scans the entire table | Sergei Kornilov | 12:47 |
| Re: Partial index creation always scans the entire table | Justin Pryzby | 12:53 |
| Re: Partial index creation always scans the entire table | Laurenz Albe | 21:15 |
| Thread | Author | Time |
|---|---|---|
| Re: Partial index creation always scans the entire table | Tom Lane | 15:30 |
| Re: Partial index creation always scans the entire table | Justin Pryzby | 15:59 |
| Re: Partial index creation always scans the entire table | Tom Lane | 16:35 |
| SubtransControlLock and performance problems | Lars Aksel Opsahl | 17:15 |
| Thread | Author | Time |
|---|---|---|
| RE: Partial index creation always scans the entire table | Mike Sofen | 00:43 |
| Re: Partial index creation always scans the entire table | Justin Pryzby | 00:52 |
| Re: Partial index creation always scans the entire table | Tom Lane | 01:09 |
| Re: SubtransControlLock and performance problems | Laurenz Albe | 09:53 |
| Re: SubtransControlLock and performance problems | Lars Aksel Opsahl | 15:03 |
| Re: SubtransControlLock and performance problems | Laurenz Albe | 16:35 |
| Re: SubtransControlLock and performance problems | Pavel Stehule | 18:01 |
| Re: SubtransControlLock and performance problems | Tom Lane | 18:23 |
| Re: SubtransControlLock and performance problems | Pavel Stehule | 18:41 |
| Re: SubtransControlLock and performance problems | Alvaro Herrera | 19:10 |
| Thread | Author | Time |
|---|---|---|
| Re: SubtransControlLock and performance problems | Laurenz Albe | 17:27 |
| DB running out of memory issues after upgrade | Nagaraj Raj | 17:46 |
| Re: DB running out of memory issues after upgrade | Tomas Vondra | 17:58 |
| Re: DB running out of memory issues after upgrade | Tom Lane | 18:07 |
| Re: DB running out of memory issues after upgrade | Nagaraj Raj | 18:10 |
| Re: DB running out of memory issues after upgrade | Stephen Frost | 18:33 |
| Re: DB running out of memory issues after upgrade | Merlin Moncure | 18:38 |
| Re: DB running out of memory issues after upgrade | Justin Pryzby | 18:40 |
| Re: DB running out of memory issues after upgrade | Merlin Moncure | 18:49 |
| Re: DB running out of memory issues after upgrade | Nagaraj Raj | 19:10 |
| Re: SubtransControlLock and performance problems | Pavel Stehule | 23:46 |
| Thread | Author | Time |
|---|---|---|
| tablespace to benefit from ssd ? | Nicolas PARIS | 04:42 |
| Re: tablespace to benefit from ssd ? | Sebastiaan Mannem | 08:02 |
| Re: tablespace to benefit from ssd ? | Laurenz Albe | 10:48 |
| Re: SubtransControlLock and performance problems | Lars Aksel Opsahl | 10:49 |
| Re: tablespace to benefit from ssd ? | Justin Pryzby | 13:08 |
| Re: SubtransControlLock and performance problems | Alvaro Herrera | 15:23 |
| Thread | Author | Time |
|---|---|---|
| Re: How to avoid UPDATE performance degradation in a transaction | Andres Freund | 04:35 |
| Re: SubtransControlLock and performance problems | Lars Aksel Opsahl | 09:20 |
| Re: tablespace to benefit from ssd ? | Jeff Janes | 17:30 |
| Thread | Author | Time |
|---|---|---|
| RE: Can we have multiple tablespaces with in a database. | Daulat Ram | 04:45 |
| Thread | Author | Time |
|---|---|---|
| PostgreSQL 11 higher Planning time on Partitioned table | Ravi Garg | 09:56 |
| Re: PostgreSQL 11 higher Planning time on Partitioned table | Justin Pryzby | 10:12 |
| Re: DB running out of memory issues after upgrade | Peter J. Holzer | 10:19 |
| Re: PostgreSQL 11 higher Planning time on Partitioned table | Justin Pryzby | 10:46 |
| Re: PostgreSQL 11 higher Planning time on Partitioned table 📎 | Ravi Garg | 10:57 |
| Re: PostgreSQL 11 higher Planning time on Partitioned table | Justin Pryzby | 15:10 |
| Re: PostgreSQL 11 higher Planning time on Partitioned table | Imre Samu | 16:18 |
| Thread | Author | Time |
|---|---|---|
| Re: DB running out of memory issues after upgrade | Merlin Moncure | 16:34 |
| Re: PostgreSQL 11 higher Planning time on Partitioned table | Ravi Garg | 19:40 |
| Re: PostgreSQL 11 higher Planning time on Partitioned table | Ravi Garg | 19:44 |
| LDAP with TLS is taking more time in Postgresql 11.5 | Mani Sankar | 19:50 |
| Re: LDAP with TLS is taking more time in Postgresql 11.5 | Adrian Klaver | 20:58 |
| Thread | Author | Time |
|---|---|---|
| Re: LDAP with TLS is taking more time in Postgresql 11.5 | Thomas Munro | 01:14 |
| Re: proposal: schema variables | remi duval | 14:53 |
| much slower query in production | Guillaume Cottenceau | 16:17 |
| Re: much slower query in production | Justin Pryzby | 16:28 |
| Re: much slower query in production | Michael Lewis | 16:52 |
| Re: much slower query in production | Guillaume Cottenceau | 18:02 |
| Re: much slower query in production | Guillaume Cottenceau | 18:04 |
| Re: much slower query in production | Michael Lewis | 18:18 |
| Re: much slower query in production | [email protected] | 19:18 |
| Re: much slower query in production | Guillaume Cottenceau | 19:37 |
| Re: proposal: schema variables 📎 | Pavel Stehule | 20:40 |
| Re: much slower query in production | Jeff Janes | 22:59 |
| Re: much slower query in production | Jeff Janes | 23:17 |
| Thread | Author | Time |
|---|---|---|
| Re: much slower query in production | Guillaume Cottenceau | 08:31 |
| Re: proposal: schema variables | Pavel Stehule | 14:37 |
| RE: proposal: schema variables | DUVAL REMI | 14:59 |