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 |
|---|---|---|
| pgstattuple_approx for toasted table | Mariel Cherkassky | 15:59 |
| Re: [HACKERS] proposal: schema variables 📎 | Pavel Stehule | 20:27 |
| Thread | Author | Time |
|---|---|---|
| Re: pgstattuple_approx for toasted table | Laurenz Albe | 05:21 |
| Thread | Author | Time |
|---|---|---|
| Server upgrade advice [xpost] | Rory Campbell-Lange | 22:03 |
| Thread | Author | Time |
|---|---|---|
| Re: Server upgrade advice [xpost] | Ian Harding | 05:04 |
| autovacuum just stop vacuuming specific table for 7 hours | Mariel Cherkassky | 16:47 |
| Re: autovacuum just stop vacuuming specific table for 7 hours | Justin Pryzby | 17:05 |
| JIT performance question | Tobias Gierke | 17:16 |
| Re: autovacuum just stop vacuuming specific table for 7 hours | Mariel Cherkassky | 17:16 |
| Re: JIT performance question | Andres Freund | 17:42 |
| Re: JIT performance question | Tobias Gierke | 18:21 |
| Re: JIT performance question | Andres Freund | 18:32 |
| Good afternoon. | Kenia Vergara | 20:09 |
| Performance regressions found using sqlfuzz | Jinho Jung | 21:41 |
| rusage (Re: Good afternoon.) | Justin Pryzby | 22:48 |
| Re: rusage (Re: Good afternoon.) | Julien Rouhaud | 22:59 |
| Thread | Author | Time |
|---|---|---|
| Re: Re: [HACKERS] proposal: schema variables | David Steele | 06:52 |
| Re: Re: [HACKERS] proposal: schema variables | Fabien COELHO | 08:10 |
| Re: Re: [HACKERS] proposal: schema variables | Pavel Stehule | 08:32 |
| Re: Re: [HACKERS] proposal: schema variables | Pavel Stehule | 08:37 |
| Re: [HACKERS] proposal: schema variables | David Steele | 09:26 |
| Thread | Author | Time |
|---|---|---|
| IS NOT DISTINCT FROM statement | Artur Zając | 11:30 |
| Re: IS NOT DISTINCT FROM statement | Laurenz Albe | 11:45 |
| Re: IS NOT DISTINCT FROM statement | David Rowley | 12:13 |
| RE: IS NOT DISTINCT FROM statement | Artur Zając | 12:25 |
| Re: IS NOT DISTINCT FROM statement | David Rowley | 13:12 |
| Hot to model data in DB (PostgreSQL) for SNMP-like multiple configurations | Alexandru Lazarev | 14:39 |
| Re: IS NOT DISTINCT FROM statement | Tom Lane | 14:53 |
| Re: Hot to model data in DB (PostgreSQL) for SNMP-like multiple configurations | Alban Hertroys | 15:15 |
| Re: Hot to model data in DB (PostgreSQL) for SNMP-like multiple configurations | Alexandru Lazarev | 16:40 |
| Thread | Author | Time |
|---|---|---|
| Re: Hot to model data in DB (PostgreSQL) for SNMP-like multiple configurations | Rene Romero Benavides | 20:08 |
| Thread | Author | Time |
|---|---|---|
| Shared_buffers | Daulat Ram | 08:12 |
| Wired execution in my benchmark using postgresql 9.6 | tayeb merabti | 14:14 |
| Performance regression related to parallel execution | Jinho Jung | 19:19 |
| Thread | Author | Time |
|---|---|---|
| Re: ERROR: found xmin from before relfrozenxid | Mariel Cherkassky | 07:58 |
| Re: Shared_buffers | Laurenz Albe | 08:29 |
| Re: Shared_buffers | Michael Lewis | 19:23 |
| Re: Shared_buffers | MichaelDBA | 20:03 |
| Re: Shared_buffers | Justin Pryzby | 20:11 |
| Re: Shared_buffers | MichaelDBA | 20:11 |
| Thread | Author | Time |
|---|---|---|
| Planner not choosing GIN index | Corey Huinker | 01:44 |
| Re: Planner not choosing GIN index | Flo Rance | 09:10 |
| Re: ERROR: found xmin from before relfrozenxid | Adrien NAYRAT | 12:24 |
| Re: ERROR: found xmin from before relfrozenxid | Mariel Cherkassky | 12:29 |
| Re: ERROR: found xmin from before relfrozenxid | Alexandre Arruda | 12:48 |
| Re: ERROR: found xmin from before relfrozenxid | Mariel Cherkassky | 12:59 |
| Re: Planner not choosing GIN index | Corey Huinker | 13:55 |
| Re: Planner not choosing GIN index | Flo Rance | 14:20 |
| Re: ERROR: found xmin from before relfrozenxid | Adrien NAYRAT | 15:30 |
| Distributing data over "spindles" even on AWS EBS, (followup to the work queue saga) | Gunther | 18:44 |
| Thread | Author | Time |
|---|---|---|
| impact of auto explain on overall performance | Stephan Schmidt | 07:29 |
| Re: impact of auto explain on overall performance | Justin Pryzby | 08:23 |
| Re: impact of auto explain on overall performance | Adrien NAYRAT | 09:08 |
| Re: Distributing data over "spindles" even on AWS EBS, (followup to the work queue saga) | Gunther | 14:53 |
| Re: Distributing data over "spindles" even on AWS EBS, (followup to the work queue saga) | Jeremy Schneider | 15:11 |
| Re: Distributing data over "spindles" even on AWS EBS, (followup to the work queue saga) | Justin Pryzby | 15:54 |
| Re: impact of auto explain on overall performance | Jeff Janes | 17:50 |
| Re: impact of auto explain on overall performance | Jeremy Schneider | 19:58 |
| Thread | Author | Time |
|---|---|---|
| Facing issue in using special characters | M Tarkeshwar Rao | 05:19 |
| Re: Facing issue in using special characters | David G. Johnston | 06:33 |
| Re: Facing issue in using special characters | Gunther | 15:59 |
| jsonb_set performance degradation / multiple jsonb_set on multiple documents | Alexandru Lazarev | 16:02 |
| Re: jsonb_set performance degradation / multiple jsonb_set on multiple documents | Michel Pelletier | 16:35 |
| Re: Facing issue in using special characters | Chapman Flack | 19:26 |
| Thread | Author | Time |
|---|---|---|
| MDRaid or LSI MegaRAID? | Rory Campbell-Lange | 18:58 |
| Thread | Author | Time |
|---|---|---|
| Re: Facing issue in using special characters | Warner, Gary, Jr | 15:01 |
| Re: Distributing data over "spindles" even on AWS EBS, (followup to the work queue saga) | Gunther | 18:42 |
| Thread | Author | Time |
|---|---|---|
| Re: Facing issue in using special characters | Peter J. Holzer | 21:19 |
| Thread | Author | Time |
|---|---|---|
| Re: Distributing data over "spindles" even on AWS EBS, (followup to the work queue saga) | Sam Gendler | 15:18 |
| Thread | Author | Time |
|---|---|---|
| Performance issue with order by clause on | Maracska Ádám | 11:05 |
| Re: Performance issue with order by clause on | Corey Huinker | 17:34 |
| AW: Performance issue with order by clause on | Stephan Schmidt | 21:49 |
| Thread | Author | Time |
|---|---|---|
| Poor man's partitioned index .... not being used? | Gunther | 02:45 |
| Re: Poor man's partitioned index .... not being used? | David Rowley | 03:34 |
| Re: Poor man's partitioned index .... not being used? | Andrew Gierth | 03:46 |
| Re: Poor man's partitioned index .... not being used? | Gunther | 18:57 |
| EXPLAIN PLAN for DELETE CASCADE or DELETE not using pkey index despite EXPLAINing that it would? | Gunther | 19:31 |
| Re: EXPLAIN PLAN for DELETE CASCADE or DELETE not using pkey index despite EXPLAINing that it would? | Tom Lane | 21:16 |
| Thread | Author | Time |
|---|---|---|
| Re: Poor man's partitioned index .... not being used? | David Rowley | 12:56 |
| Re: EXPLAIN PLAN for DELETE CASCADE or DELETE not using pkey index despite EXPLAINing that it would? | Gunther | 20:01 |
| Re: EXPLAIN PLAN for DELETE CASCADE or DELETE not using pkey index despite EXPLAINing that it would? | Justin Pryzby | 20:07 |
| Thread | Author | Time |
|---|---|---|
| Re: [HACKERS] proposal: schema variables 📎 | Pavel Stehule | 05:57 |
| Re: [HACKERS] proposal: schema variables | Erik Rijkers | 09:25 |
| Re: [HACKERS] proposal: schema variables | Pavel Stehule | 09:32 |
| Thread | Author | Time |
|---|---|---|
| Re: [HACKERS] proposal: schema variables | Erik Rijkers | 19:40 |
| Thread | Author | Time |
|---|---|---|
| Re: [HACKERS] proposal: schema variables 📎 | Pavel Stehule | 05:40 |
| Re: [HACKERS] proposal: schema variables | Pavel Stehule | 05:41 |
| Thread | Author | Time |
|---|---|---|
| trying to analyze deadlock | Mariel Cherkassky | 12:52 |
| Re: trying to analyze deadlock | Laurenz Albe | 13:17 |
| Re: trying to analyze deadlock | Laurenz Albe | 13:19 |
| Thread | Author | Time |
|---|---|---|
| Scale out postgresql | Mariel Cherkassky | 10:10 |
| Re: Scale out postgresql | Sam R. | 16:10 |
| Re: Scale out postgresql | Mariel Cherkassky | 16:19 |
| Re: Scale out postgresql | Sumedh Pathak | 16:26 |
| LIMIT OFFSET with DB view vs plain SQL | Raj Gandhi | 22:41 |
| Re: LIMIT OFFSET with DB view vs plain SQL | Raj Gandhi | 22:43 |
| Thread | Author | Time |
|---|---|---|
| Re: LIMIT OFFSET with DB view vs plain SQL | Laurenz Albe | 13:53 |
| endless quere when upsert with ON CONFLICT clause | Stephan Schmidt | 14:29 |
| Re: LIMIT OFFSET with DB view vs plain SQL | Merlin Moncure | 15:28 |
| Re: endless quere when upsert with ON CONFLICT clause | Andreas Kretschmer | 16:00 |
| Need advice: Parallel query execution introduces performance regression | Jinho Jung | 16:06 |
| Re: LIMIT OFFSET with DB view vs plain SQL | Raj Gandhi | 23:38 |
| Thread | Author | Time |
|---|---|---|
| Postgresql Sort cost Poor performance? | tank.zhang | 09:45 |
| Fwd: trying to analyze deadlock | Mariel Cherkassky | 10:16 |
| Re: Postgresql Sort cost Poor performance? | Andrew Gierth | 10:20 |
| Re: Postgresql Sort cost Poor performance? | tank.zhang | 10:30 |
| Re: Postgresql Sort cost Poor performance? | Gavin Flower | 10:32 |
| Re: Postgresql Sort cost Poor performance? | Christoph Berg | 10:54 |
| Re: trying to analyze deadlock | Mariel Cherkassky | 11:20 |
| Re: Good afternoon. | Rafia Sabih | 13:03 |
| Re: LIMIT OFFSET with DB view vs plain SQL | Raj Gandhi | 13:56 |
| Thread | Author | Time |
|---|---|---|
| Re: LIMIT OFFSET with DB view vs plain SQL | Raj Gandhi | 02:06 |
| Re: LIMIT OFFSET with DB view vs plain SQL | SAMEER KUMAR | 04:16 |
| Re: LIMIT OFFSET with DB view vs plain SQL | Ramón Bastidas | 04:49 |
| Re: Good afternoon. | Ramón Bastidas | 05:03 |
| Re: Postgresql Sort cost Poor performance? | Ramón Bastidas | 05:25 |
| Re: Postgresql Sort cost Poor performance? | tank.zhang | 07:00 |
| Re: Postgresql Sort cost Poor performance? | David Rowley | 07:42 |
| Re: Postgresql Sort cost Poor performance? | tank.zhang | 08:23 |
| [No subject] | Mariel Cherkassky | 08:32 |
| Re: parallel query | Laurenz Albe | 11:28 |
| Re: trying to analyze deadlock | Shreeyansh Dba | 12:21 |
| Re: [HACKERS] proposal: schema variables 📎 | Pavel Stehule | 18:02 |
| Thread | Author | Time |
|---|---|---|
| Commit(?) overhead | Duncan Kinnear | 21:59 |
| Thread | Author | Time |
|---|---|---|
| RAM usage of PostgreSql | Prasad | 14:48 |
| Re: Commit(?) overhead | Jeff Janes | 15:14 |
| monitoring options for postgresql under AWS/RDS? | Mamet, Eric (GfK) | 16:28 |
| Re: monitoring options for postgresql under AWS/RDS? | Justin Pryzby | 17:43 |
| Re: RAM usage of PostgreSql | Justin Pryzby | 17:46 |
| Re: monitoring options for postgresql under AWS/RDS? | Rijo Roy | 18:03 |
| Re: RAM usage of PostgreSql | Laurenz Albe | 18:08 |
| Re: RAM usage of PostgreSql | Keith | 18:09 |
| Thread | Author | Time |
|---|---|---|
| RE: monitoring options for postgresql under AWS/RDS? | Mamet, Eric (GfK) | 09:46 |
| Re: monitoring options for postgresql under AWS/RDS? | Praveen Duraiswami | 12:57 |
| Thread | Author | Time |
|---|---|---|
| Re: Commit(?) overhead | Duncan Kinnear | 21:26 |
| Re: Commit(?) overhead | Justin Pryzby | 22:12 |
| Re: Commit(?) overhead | Andres Freund | 22:23 |
| Re: Commit(?) overhead | Duncan Kinnear | 22:42 |
| Thread | Author | Time |
|---|---|---|
| PostgreSQL upgrade. | Daulat Ram | 05:40 |
| Re: Commit(?) overhead | Laurenz Albe | 08:16 |
| Re: PostgreSQL upgrade. | Andreas Kretschmer | 08:20 |
| Thread | Author | Time |
|---|---|---|
| Out of Memory errors are frustrating as heck! | Gunther | 20:23 |
| Re: Out of Memory errors are frustrating as heck! | Tom Lane | 21:19 |
| Re: Out of Memory errors are frustrating as heck! | Jeff Janes | 21:19 |
| Thread | Author | Time |
|---|---|---|
| Re: Out of Memory errors are frustrating as heck! | Gunther | 01:49 |
| Re: PostgreSQL upgrade. 📎 | Mark Kirkwood | 02:08 |
| Re: Out of Memory errors are frustrating as heck! | Tom Lane | 02:28 |
| Re: Out of Memory errors are frustrating as heck! | Alvaro Herrera | 02:39 |
| Re: Out of Memory errors are frustrating as heck! | Gunther | 02:39 |
| Re: Out of Memory errors are frustrating as heck! | Tom Lane | 02:50 |
| Re: Out of Memory errors are frustrating as heck! | Tom Lane | 03:03 |
| Re: Out of Memory errors are frustrating as heck! | Gunther | 05:23 |
| Re: Out of Memory errors are frustrating as heck! | Gunther | 06:33 |
| Re: Out of Memory errors are frustrating as heck! | Tom Lane | 15:30 |
| Postgres backup & restore | Daulat Ram | 17:41 |
| Re: Postgres backup & restore | Justin Pryzby | 17:54 |
| Re: Out of Memory errors are frustrating as heck! | Jeff Janes | 19:28 |