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 | Tomas Vondra | 01:20 |
| Re: PATCH: adaptive ndistinct estimator v4 | Tomas Vondra | 01:24 |
| Index Scan Backward Slow | David Osborne | 10:54 |
| Re: Index Scan Backward Slow | Evgeniy Shishkin | 10:59 |
| Re: Index Scan Backward Slow | David Osborne | 11:06 |
| Re: PATCH: adaptive ndistinct estimator v4 | Robert Haas | 11:55 |
| Thread | Author | Time |
|---|---|---|
| Re: Index Scan Backward Slow | Robert Klemme | 08:48 |
| Thread | Author | Time |
|---|---|---|
| optimization join on random value | Anton Bushmelev | 21:23 |
| Re: optimization join on random value | Heikki Linnakangas | 21:28 |
| Thread | Author | Time |
|---|---|---|
| How to clean/truncate / VACUUM FULL pg_largeobject without (much) downtime? | Muthusamy, Sivaraman | 09:55 |
| Thread | Author | Time |
|---|---|---|
| Re: PATCH: adaptive ndistinct estimator v4 | Jeff Janes | 21:07 |
| 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 |