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: PATCH: adaptive ndistinct estimator v4 | Robert Haas | 18:30 |
| Re: PATCH: adaptive ndistinct estimator v4 | Josh Berkus | 19:35 |
| Re: PATCH: adaptive ndistinct estimator v4 | Robert Haas | 19:58 |
| Re: PATCH: adaptive ndistinct estimator v4 | Josh Berkus | 20:00 |
| Thread | Author | Time |
|---|---|---|
| Re: Fastest way / best practice to calculate "next birthdays" | er.tejaspatel88@gmail.com | 09:30 |
| Thread | Author | Time |
|---|---|---|
| Re: Fastest way / best practice to calculate "next birthdays" | David G. Johnston | 03:22 |
| union all and filter / index scan -> seq scan | Florian Lohoff | 10:41 |
| Re: union all and filter / index scan -> seq scan | Vitalii Tymchyshyn | 15:09 |
| Re: union all and filter / index scan -> seq scan | Tom Lane | 15:28 |
| Re: Fastest way / best practice to calculate "next birthdays" | Bosco Rama | 16:15 |
| Re: Fastest way / best practice to calculate "next birthdays" | David G. Johnston | 16:50 |
| Re: PostgreSQL disk fragmentation causes performance problems on Windows | Josh Berkus | 18:54 |
| Re: PostgreSQL disk fragmentation causes performance problems on Windows | Andres Freund | 20:39 |
| Re: PostgreSQL disk fragmentation causes performance problems on Windows | Vitalii Tymchyshyn | 23:16 |
| Thread | Author | Time |
|---|---|---|
| Re: PostgreSQL disk fragmentation causes performance problems on Windows | Josh Berkus | 17:34 |
| Re: How to clean/truncate / VACUUM FULL pg_largeobject without (much) downtime? | Jim Nasby | 21:17 |
| Re: Fastest way / best practice to calculate "next birthdays" | Jim Nasby | 21:23 |
| MAX() and multi-column index on a partitioned table? | Dave Johansen | 22:27 |
| Re: MAX() and multi-column index on a partitioned table? | Tom Lane | 22:42 |
| Re: MAX() and multi-column index on a partitioned table? | Dave Johansen | 23:53 |
| Thread | Author | Time |
|---|---|---|
| Re: MAX() and multi-column index on a partitioned table? | Tom Lane | 01:13 |
| Thread | Author | Time |
|---|---|---|
| ERROR: missing chunk number 0 for toast value 1821556134 in pg_toast_17881 | Tory M Blue | 07:50 |
| Fastest Backup & Restore for perf testing | Wes Vaske (wvaske) | 20:24 |
| Re: Fastest Backup & Restore for perf testing | Andrew Dunstan | 20:37 |
| Re: Fastest Backup & Restore for perf testing | Steve Atkins | 20:39 |
| Re: ERROR: missing chunk number 0 for toast value 1821556134 in pg_toast_17881 | Josh Berkus | 22:02 |
| Thread | Author | Time |
|---|---|---|
| Postmaster eating up all my cpu | birimblongas | 11:25 |
| Partitioning and performance | Ravi Krishna | 14:31 |
| Re: Partitioning and performance | Ravi Krishna | 14:41 |
| Re: Fastest Backup & Restore for perf testing | Jim Nasby | 17:40 |
| Re: Partitioning and performance | Jim Nasby | 18:05 |
| Thread | Author | Time |
|---|---|---|
| Different plan for very similar queries | Peter J. Holzer | 08:55 |
| Re: Different plan for very similar queries | Peter J. Holzer | 09:51 |
| Postgres is using 100% CPU | Ashik S L | 16:40 |
| Re: Postgres is using 100% CPU | Tomas Vondra | 17:17 |
| Re: Postgres is using 100% CPU | Tomas Vondra | 17:18 |
| Fwd: Postgres is using 100% CPU | Ashik S L | 17:57 |
| Postgres is using 100% CPU | Ashik S L | 18:10 |
| Re: Postgres is using 100% CPU | Yves Dorfsman | 18:30 |
| Re: Postgres is using 100% CPU | Tomas Vondra | 19:20 |
| Re: Different plan for very similar queries | Tomas Vondra | 23:47 |
| Thread | Author | Time |
|---|---|---|
| Re: Postgres is using 100% CPU | Ashik S L | 13:46 |
| Re: Postgres is using 100% CPU | Tomas Vondra | 14:20 |
| Re: Different plan for very similar queries | Tom Lane | 19:04 |
| Re: Postmaster eating up all my cpu | Tomas Vondra | 20:45 |
| Thread | Author | Time |
|---|---|---|
| Re: Different plan for very similar queries | Peter J. Holzer | 11:00 |
| Re: Postgres is using 100% CPU | Jean-David Beyer | 13:04 |
| Re: Postgres is using 100% CPU | Yves Dorfsman | 14:23 |
| Re: Different plan for very similar queries | Tom Lane | 15:50 |
| Re: Different plan for very similar queries | Tomas Vondra | 16:05 |
| Re: Different plan for very similar queries | Tom Lane | 16:22 |
| Re: Different plan for very similar queries | Tomas Vondra | 16:39 |
| Thread | Author | Time |
|---|---|---|
| Re: Postgres is using 100% CPU | Ashik S L | 05:38 |
| Re: Postgres is using 100% CPU | Merlin Moncure | 13:20 |
| Slow hash join performance with many batches 📎 | Alex Adriaanse | 16:03 |
| Re: Slow hash join performance with many batches | Tom Lane | 17:58 |
| Re: Fastest way / best practice to calculate "next birthdays" | Kevin Grittner | 19:11 |
| Re: Postgres is using 100% CPU | Scott Marlowe | 19:35 |
| Connection time when using SSL | Marco Di Cesare | 20:51 |
| Re: Connection time when using SSL | Tomas Vondra | 21:21 |
| Thread | Author | Time |
|---|---|---|
| Re: Postgres is using 100% CPU | Graeme B. Bell | 07:47 |
| Re: Postgres is using 100% CPU | Graeme B. Bell | 07:58 |
| Re: Postgres is using 100% CPU | Ashik S L | 08:20 |
| Thread | Author | Time |
|---|---|---|
| Re: How to reduce writing on disk ? (90 gb on pgsql_tmp) | Tomas Vondra | 00:22 |
| Re: How to reduce writing on disk ? (90 gb on pgsql_tmp) | Scott Marlowe | 00:53 |
| Re: How to reduce writing on disk ? (90 gb on pgsql_tmp) | Scott Marlowe | 00:58 |
| Re: How to reduce writing on disk ? (90 gb on pgsql_tmp) | Mark Kirkwood | 01:19 |
| Need more IOPS? This should get you drooling... (5xnvme drives) | Graeme B. Bell | 11:07 |
| Re: Need more IOPS? This should get you drooling... (5xnvme drives) | Graeme B. Bell | 11:23 |
| Re: Need more IOPS? This should get you drooling... (5xnvme drives) | Dorian Hoxha | 11:29 |
| Re: Need more IOPS? This should get you drooling... (5xnvme drives) | Graeme B. Bell | 11:35 |
| Re: How to reduce writing on disk ? (90 gb on pgsql_tmp) | Tomas Vondra | 14:43 |
| Thread | Author | Time |
|---|---|---|
| Query running slow for only one specific id. (Postgres 9.3) version | Sheena, Prabhjot | 17:54 |
| Re: Query running slow for only one specific id. (Postgres 9.3) version | Igor Neyman | 18:05 |
| Re: Query running slow for only one specific id. (Postgres 9.3) version | Steve Crawford | 18:24 |
| Re: Query running slow for only one specific id. (Postgres 9.3) version | Sheena, Prabhjot | 18:38 |
| Re: Query running slow for only one specific id. (Postgres 9.3) version | Igor Neyman | 18:46 |
| Re: Re: Query running slow for only one specific id. (Postgres 9.3) version | Steve Crawford | 19:28 |
| Re: Re: [GENERAL] Re: Query running slow for only one specific id. (Postgres 9.3) version | Steve Crawford | 19:34 |
| Re: [PERFORM] Query running slow for only one specific id. (Postgres 9.3) version | Matheus de Oliveira | 22:34 |
| Thread | Author | Time |
|---|---|---|
| Re: How to reduce writing on disk ? (90 gb on pgsql_tmp) | ben.play | 15:58 |
| Re: How to reduce writing on disk ? (90 gb on pgsql_tmp) | Claudio Freire | 16:04 |
| Thread | Author | Time |
|---|---|---|
| Slow query - lots of temporary files. | Johann Spies | 12:39 |
| Re: Slow query - lots of temporary files. | Claudio Freire | 13:02 |
| Re: Slow query - lots of temporary files. | Johann Spies | 13:42 |
| Re: Slow query - lots of temporary files. | Tomas Vondra | 14:50 |
| Row estimates off by two orders of magnitude with hstore | Patrick Krecker | 17:32 |
| Re: Row estimates off by two orders of magnitude with hstore | Merlin Moncure | 18:32 |
| Re: Row estimates off by two orders of magnitude with hstore | Josh Berkus | 19:40 |
| Re: Row estimates off by two orders of magnitude with hstore | Merlin Moncure | 20:01 |
| Re: Row estimates off by two orders of magnitude with hstore | Patrick Krecker | 20:55 |
| Re: Row estimates off by two orders of magnitude with hstore | Merlin Moncure | 21:08 |
| Re: Row estimates off by two orders of magnitude with hstore | Patrick Krecker | 21:37 |
| Re: Row estimates off by two orders of magnitude with hstore | Merlin Moncure | 22:08 |
| Thread | Author | Time |
|---|---|---|
| Re: How to reduce writing on disk ? (90 gb on pgsql_tmp) | ben.play | 08:56 |
| Re: How to reduce writing on disk ? (90 gb on pgsql_tmp) | Claudio Freire | 12:48 |
| Thread | Author | Time |
|---|---|---|
| Do work_mem and shared buffers have 1g or 2g limit on 64 bit linux? | Kaijiang Chen | 17:27 |
| Re: Do work_mem and shared buffers have 1g or 2g limit on 64 bit linux? | Joshua D. Drake | 17:43 |
| Re: Do work_mem and shared buffers have 1g or 2g limit on 64 bit linux? | Joe Conway | 18:10 |
| Thread | Author | Time |
|---|---|---|
| Re: Do work_mem and shared buffers have 1g or 2g limit on 64 bit linux? | Kaijiang Chen | 03:44 |
| Re: Slow query: Postgres chooses nested loop over hash join, whery by hash join is much faster, wrong number of rows estimated | Merlin Moncure | 14:25 |
| Re: Do work_mem and shared buffers have 1g or 2g limit on 64 bit linux? | Tomas Vondra | 14:57 |
| Thread | Author | Time |
|---|---|---|
| Re: PATCH: adaptive ndistinct estimator v4 📎 | Tomas Vondra | 14:47 |
| Thread | Author | Time |
|---|---|---|
| Re: Techniques to Avoid Temp Files | Albe Laurenz | 08:17 |
| Slow query (planner insisting on using 'external merge' sort type) | Ian Pushee | 14:34 |
| Re: Slow query (planner insisting on using 'external merge' sort type) | Igor Neyman | 14:46 |
| Re: Slow query (planner insisting on using 'external merge' sort type) | Andreas Kretschmer | 14:47 |
| Re: Slow query (planner insisting on using 'external merge' sort type) | Ian Pushee | 14:53 |
| Re: Slow query (planner insisting on using 'external merge' sort type) | Ian Pushee | 14:57 |
| Re: Slow query (planner insisting on using 'external merge' sort type) | Igor Neyman | 15:06 |
| Re: Slow query (planner insisting on using 'external merge' sort type) | Igor Neyman | 15:18 |
| Re: Techniques to Avoid Temp Files | Jeff Janes | 18:26 |
| Thread | Author | Time |
|---|---|---|
| Re: Slow query (planner insisting on using 'external merge' sort type) | Jim Nasby | 21:05 |
| Thread | Author | Time |
|---|---|---|
| pgbouncer issue | Sheena, Prabhjot | 18:09 |
| Thread | Author | Time |
|---|---|---|
| Re: Slow query (planner insisting on using 'external merge' sort type) | Mark Kirkwood | 02:01 |
| Thread | Author | Time |
|---|---|---|
| Does anyone have python code which digests pgbench -r output? | Josh Berkus | 19:29 |
| Thread | Author | Time |
|---|---|---|
| Sudden connection and load average spikes with postgresql 9.3 | eudald_v | 14:52 |
| Re: Sudden connection and load average spikes with postgresql 9.3 | Tom Lane | 15:37 |
| Re: Sudden connection and load average spikes with postgresql 9.3 | eudald_v | 16:08 |
| Re: Sudden connection and load average spikes with postgresql 9.3 | Josh Berkus | 22:56 |
| Thread | Author | Time |
|---|---|---|
| New server: SSD/RAID recommendations? | Craig James | 23:06 |
| Re: New server: SSD/RAID recommendations? | Andreas Joseph Krogh | 23:56 |
| Re: New server: SSD/RAID recommendations? | Scott Marlowe | 23:57 |
| Thread | Author | Time |
|---|---|---|
| Re: New server: SSD/RAID recommendations? | Wes Vaske (wvaske) | 14:01 |
| Re: New server: SSD/RAID recommendations? | Merlin Moncure | 14:25 |
| Re: Sudden connection and load average spikes with postgresql 9.3 | eudald_v | 15:41 |
| Hmmm... why does CPU-intensive pl/pgsql code parallelise so badly when queries parallelise fine? Anyone else seen this? | Graeme B. Bell | 16:15 |
| Re: New server: SSD/RAID recommendations? | Craig James | 17:20 |
| Re: New server: SSD/RAID recommendations? | Craig James | 17:22 |
| Re: New server: SSD/RAID recommendations? | Craig James | 17:44 |
| Re: New server: SSD/RAID recommendations? | Wes Vaske (wvaske) | 18:00 |
| Re: Sudden connection and load average spikes with postgresql 9.3 | Josh Berkus | 19:31 |
| Re: Sudden connection and load average spikes with postgresql 9.3 | Josh Berkus | 19:33 |
| Re: Sudden connection and load average spikes with postgresql 9.3 | Kevin Grittner | 21:13 |
| Re: Sudden connection and load average spikes with postgresql 9.3 | Scott Marlowe | 23:04 |
| Thread | Author | Time |
|---|---|---|
| Hmmm... why does pl/pgsql code parallelise so badly when queries parallelise fine? Anyone else seen this? | Graeme B. Bell | 14:48 |
| Re: Hmmm... why does pl/pgsql code parallelise so badly when queries parallelise fine? Anyone else seen this? | Marc Mamin | 16:15 |
| Thread | Author | Time |
|---|---|---|
| 9.5alpha1 vs 9.4 | Mkrtchyan, Tigran | 11:10 |
| Re: 9.5alpha1 vs 9.4 | Mkrtchyan, Tigran | 11:46 |
| Re: 9.5alpha1 vs 9.4 | Andres Freund | 12:54 |
| Re: 9.5alpha1 vs 9.4 | Tom Lane | 14:33 |
| Re: pgbouncer issue | Greg Sabino Mullane | 14:47 |
| Re: 9.5alpha1 vs 9.4 | Mkrtchyan, Tigran | 17:16 |
| Thread | Author | Time |
|---|---|---|
| Re: Hmmm... why does pl/pgsql code parallelise so badly when queries parallelise fine? Anyone else seen this? | Merlin Moncure | 16:40 |
| Re: 9.5alpha1 vs 9.4 | Josh Berkus | 16:45 |
| Re: New server: SSD/RAID recommendations? | Steve Crawford | 16:56 |
| Re: New server: SSD/RAID recommendations? | Joshua D. Drake | 17:20 |
| Re: 9.5alpha1 vs 9.4 | Mkrtchyan, Tigran | 21:14 |
| Thread | Author | Time |
|---|---|---|
| Re: New server: SSD/RAID recommendations? | Graeme B. Bell | 10:22 |
| Re: New server: SSD/RAID recommendations? | Mkrtchyan, Tigran | 10:28 |
| Re: New server: SSD/RAID recommendations? | Graeme B. Bell | 10:38 |
| Re: New server: SSD/RAID recommendations? 📎 | Mkrtchyan, Tigran | 10:56 |
| Re: New server: SSD/RAID recommendations? | Karl Denninger | 11:28 |
| Re: Sudden connection and load average spikes with postgresql 9.3 | eudald_v | 11:29 |
| Re: New server: SSD/RAID recommendations? | Graeme B. Bell | 11:52 |
| Re: New server: SSD/RAID recommendations? | Graeme B. Bell | 12:04 |