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: REPOST: Nested loops row estimates always too high | Ow Mun Heng | 00:50 |
Re: REPOST: Nested loops row estimates always too high | Carlo Stonebanks | 04:53 |
Re: REPOST: Nested loops row estimates always too high | Ow Mun Heng | 05:15 |
Re: REPOST: Nested loops row estimates always too high | Steinar H. Gunderson | 09:31 |
Attempting to disable count triggers on cleanup | Dave Cramer | 11:08 |
Re: Attempting to disable count triggers on cleanup | hubert depesz lubaczewski | 11:21 |
Re: Attempting to disable count triggers on cleanup | Dave Cramer | 11:39 |
Re: query io stats and finding a slow query | Kamen Stanev | 19:41 |
Re: query io stats and finding a slow query | Bryan Murphy | 19:58 |
Thread | Author | Time |
---|---|---|
Re: REPOST: Nested loops row estimates always too high | Ow Mun Heng | 03:50 |
Re: REPOST: Nested loops row estimates always too high | Tom Lane | 04:02 |
Re: Effects of cascading references in foreign keys | Bruce Momjian | 08:21 |
Incorrect row estimates in plan? | pgdba | 14:22 |
Re: Incorrect row estimates in plan? | Tom Lane | 14:45 |
Re: Searching for the cause of a bad plan 📎 | Csaba Nagy | 14:52 |
Re: Searching for the cause of a bad plan | Tom Lane | 15:22 |
Re: Incorrect row estimates in plan? | pgdba | 15:24 |
Re: Incorrect row estimates in plan? | Tom Lane | 16:38 |
Re: Incorrect row estimates in plan? | pgdba | 16:56 |
Difference in query plan when using = or > in where clause | Radhika S | 18:00 |
Thread | Author | Time |
---|---|---|
Re: REPOST: Nested loops row estimates always too high | Ow Mun Heng | 06:59 |
Re: Searching for the cause of a bad plan 📎 | Csaba Nagy | 11:53 |
Re: Difference in query plan when using = or > in where clause | Heikki Linnakangas | 12:39 |
Re: Searching for the cause of a bad plan | Tom Lane | 14:40 |
Re: Searching for the cause of a bad plan | Csaba Nagy | 15:16 |
Re: Searching for the cause of a bad plan | Simon Riggs | 15:24 |
Tuning for warm standby | Kevin Kempter | 17:42 |
Re: Searching for the cause of a bad plan | Ron Mayer | 18:07 |
sequence query performance issues | Peter Koczan | 22:04 |
Thread | Author | Time |
---|---|---|
Re: sequence query performance issues | Richard Huxton | 08:06 |
Re: Searching for the cause of a bad plan | Csaba Nagy | 08:12 |
Re: Searching for the cause of a bad plan | Csaba Nagy | 12:33 |
Re: Tuning for warm standby | Merlin Moncure | 13:17 |
Re: sequence query performance issues | Tom Lane | 14:16 |
Postgres 7.4.2 hanging when vacuum full is run | Radhika S | 14:28 |
Re: sequence query performance issues | Richard Huxton | 14:43 |
Re: Postgres 7.4.2 hanging when vacuum full is run | Vivek Khera | 14:53 |
Re: Postgres 7.4.2 hanging when vacuum full is run | Scott Marlowe | 15:28 |
Re: sequence query performance issues | Peter Koczan | 17:33 |
OOM Errors as a result of table inheritance and a bad plan(?) | Arctic Toucan | 17:50 |
Non-blocking vacuum full | Peter Schuller | 18:06 |
Re: Non-blocking vacuum full | Heikki Linnakangas | 19:31 |
Re: OOM Errors as a result of table inheritance and a bad plan(?) | Tom Lane | 20:56 |
Thread | Author | Time |
---|---|---|
Re: Non-blocking vacuum full | Ron Mayer | 02:46 |
Re: Non-blocking vacuum full | Heikki Linnakangas | 08:05 |
Thread | Author | Time |
---|---|---|
Re: sequence query performance issues | Peter Koczan | 19:23 |
Thread | Author | Time |
---|---|---|
Re: Linux mis-reporting memory | Decibel! | 15:57 |
Re: Linux mis-reporting memory | Scott Marlowe | 16:51 |
performance of like queries | Kevin Kempter | 17:31 |
Re: Linux mis-reporting memory | Adam Tauno Williams | 18:37 |
Re: performance of like queries | Joshua D. Drake | 21:06 |
Re: performance of like queries | Marcin Stępnicki | 21:49 |
Re: performance of like queries | Chris Browne | 21:55 |
Newbie question about degraded performance on delete statement. | Giulio Cesare Solaroli | 21:55 |
Re: Newbie question about degraded performance on delete statement. | Dan Langille | 22:02 |
Re: Linux mis-reporting memory | Decibel! | 22:17 |
Re: Newbie question about degraded performance on delete statement. | Greg Williamson | 22:39 |
Thread | Author | Time |
---|---|---|
Difference between Vacuum and Vacuum full | Radhika S | 01:45 |
Re: Difference between Vacuum and Vacuum full | Scott Marlowe | 01:55 |
Re: Difference between Vacuum and Vacuum full | Rodrigo De León | 01:56 |
Re: Difference between Vacuum and Vacuum full | D'Arcy J.M. Cain | 02:02 |
Re: Difference between Vacuum and Vacuum full | Radhika S | 03:05 |
Re: Newbie question about degraded performance on delete statement. | Giulio Cesare Solaroli | 06:56 |
Re: Newbie question about degraded performance on delete statement. (SOLVED) | Giulio Cesare Solaroli | 07:00 |
Query taking too long. Problem reading explain output. | Henrik | 08:03 |
Re: Query taking too long. Problem reading explain output. | Michael Fuhr | 13:31 |
Re: Query taking too long. Problem reading explain output. | Tom Lane | 14:15 |
Thread | Author | Time |
---|---|---|
Re: Partitioning in postgres - basic question | Chris | 05:19 |
Slow TSearch2 performance for table with 1 million documents. | Benjamin Arai | 07:50 |
Re: Slow TSearch2 performance for table with 1 million documents. | Alban Hertroys | 12:00 |
Problems with + 1 million record table | Cláudia Macedo Amorim | 14:34 |
Re: Problems with + 1 million record table | Scott Marlowe | 15:01 |
Re: Slow TSearch2 performance for table with 1 million documents. | Tom Lane | 15:12 |
Re: [PERFORM] Slow TSearch2 performance for table with 1 million documents. | Oleg Bartunov | 15:32 |
Re: Problems with + 1 million record table | Arjen van der Meijden | 16:38 |
Re: Problems with + 1 million record table | Joshua D. Drake | 17:45 |
Re: [PERFORM] Slow TSearch2 performance for table with 1 million documents. | Benjamin Arai | 22:57 |
Thread | Author | Time |
---|---|---|
Re: Problems with + 1 million record table | Shane Ambler | 01:19 |
query plan worse after analyze | Jeff Frost | 02:02 |
Re: query plan worse after analyze | Stephen Frost | 03:14 |
Re: query plan worse after analyze | Rodrigo De León | 03:58 |
Re: query plan worse after analyze | Jeff Frost | 04:12 |
Re: query plan worse after analyze | Tom Lane | 05:50 |
Re: query plan worse after analyze | Jeff Frost | 06:41 |
Re: query plan worse after analyze | Alvaro Herrera | 15:11 |
Thread | Author | Time |
---|---|---|
Apache2 PostgreSQL http authentication | Jeffrey Brower | 13:14 |
Re: Apache2 PostgreSQL http authentication | A.M. | 15:19 |
Re: query plan worse after analyze | Richard Broersma Jr | 16:06 |
Re: Apache2 PostgreSQL http authentication | Jeffrey Brower | 19:07 |
Re: Apache2 PostgreSQL http authentication | Jeffrey Brower | 20:28 |
Re: Apache2 PostgreSQL http authentication | D'Arcy J.M. Cain | 20:44 |
Re: Apache2 PostgreSQL http authentication | Jeffrey Brower | 20:58 |
Thread | Author | Time |
---|---|---|
Re: Apache2 PostgreSQL http authentication | Jeffrey Brower | 00:29 |
Re: Apache2 PostgreSQL http authentication | Magnus Hagander | 06:12 |
postgresql on NFS.. recommended? not recommended? | Gábor Farkas | 12:39 |
Re: postgresql on NFS.. recommended? not recommended? | Josh Tolley | 13:43 |
Re: Apache2 PostgreSQL http authentication | Tino Wildenhain | 17:09 |
Re: Apache2 PostgreSQL http authentication | Magnus Hagander | 17:12 |
Thread | Author | Time |
---|---|---|
SQL Monitoring | Campbell, Lance | 14:11 |
Re: SQL Monitoring | Marcin Stępnicki | 14:36 |
Re: SQL Monitoring | Heikki Linnakangas | 15:07 |
Re: SQL Monitoring | Gregory Stark | 19:00 |
Postgres running Very slowly | Radhika S | 20:00 |
hashjoin chosen over 1000x faster plan | Kevin Grittner | 20:09 |
Shared Buffer setting in postgresql.conf | Radhika S | 20:12 |
Re: Postgres running Very slowly | Bill Moran | 20:18 |
Thread | Author | Time |
---|---|---|
Re: Huge amount of memory consumed during transaction | Tom Lane | 01:26 |
Re: Performance problems with prepared statements | Theo Kramer | 07:35 |
Re: Performance problems with prepared statements | Theo Kramer | 07:38 |
Re: Performance problems with prepared statements | Theo Kramer | 08:05 |
Re: Performance problems with prepared statements | Richard Huxton | 08:26 |
Re: Performance problems with prepared statements | Merlin Moncure | 13:02 |
Re: Performance problems with prepared statements | Theo Kramer | 14:57 |
Re: Performance problems with prepared statements | Kevin Grittner | 19:03 |
Re: Huge amount of memory consumed during transaction | Tom Lane | 19:59 |
How to speed up min/max(id) in 50M rows table? | henk de wit | 20:41 |
Re: How to speed up min/max(id) in 50M rows table? | Kevin Grittner | 20:53 |
Re: How to speed up min/max(id) in 50M rows table? | henk de wit | 20:59 |
Re: Huge amount of memory consumed during transaction | henk de wit | 21:09 |
Re: How to speed up min/max(id) in 50M rows table? | henk de wit | 21:19 |