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 |
---|---|---|
multicolumn partitioning help | James Robertson | 17:59 |
Thread | Author | Time |
---|---|---|
Re: Huge Tables | Rick Otten | 12:45 |
Re: Huge Tables | André Rodrigues | 12:51 |
Thread | Author | Time |
---|---|---|
Re: multicolumn partitioning help | Justin Pryzby | 17:54 |
Re: multicolumn partitioning help | Laurenz Albe | 21:41 |
Re: multicolumn partitioning help | James Robertson | 23:33 |
Thread | Author | Time |
---|---|---|
Re: multicolumn partitioning help | Laurenz Albe | 07:37 |
Re: multicolumn partitioning help | David Rowley | 20:46 |
Re: multicolumn partitioning help | David Rowley | 21:20 |
Thread | Author | Time |
---|---|---|
Explain plan shows fewer shared blocks when index+table compared to index alone? | Amin Jaffer | 06:21 |
Re:Explain plan shows fewer shared blocks when index+table compared to index alone? | Sergei Kornilov | 07:51 |
Why are commits consuming most of the database time? | Tim Slechta | 14:46 |
Re: Why are commits consuming most of the database time? | Tom Lane | 14:57 |
Re: Why are commits consuming most of the database time? | Tim Slechta | 20:24 |
Thread | Author | Time |
---|---|---|
Query unable to utilize index without typecast to fixed length character | ahi | 10:23 |
Re: Query unable to utilize index without typecast to fixed length character | Tom Lane | 14:50 |
Thread | Author | Time |
---|---|---|
Re: Query unable to utilize index without typecast to fixed length character | ahi | 07:09 |
Is there any tool which will help me run and explain analyze about 150 queries? | kunwar singh | 17:57 |
Re: Is there any tool which will help me run and explain analyze about 150 queries? | Achilleas Mantzios | 18:19 |
Re: Is there any tool which will help me run and explain analyze about 150 queries? | kyle Hailey | 18:40 |
Re: Is there any tool which will help me run and explain analyze about 150 queries? | kunwar singh | 20:48 |
Thread | Author | Time |
---|---|---|
Re: Is there any tool which will help me run and explain analyze about 150 queries? | Jerry Sievers | 04:40 |
RE: Query unable to utilize index without typecast to fixed length character | msalais | 17:58 |
Re: Is there any tool which will help me run and explain analyze about 150 queries? | kyle Hailey | 21:44 |
Thread | Author | Time |
---|---|---|
Re: Is there any tool which will help me run and explain analyze about 150 queries? | kunwar singh | 22:15 |
Thread | Author | Time |
---|---|---|
Re: Replication lag due to lagging restart_lsn | milist ujang | 03:39 |
Thread | Author | Time |
---|---|---|
Re: Is there any tool which will help me run and explain analyze about 150 queries? | Michael Christofides | 09:17 |
Thread | Author | Time |
---|---|---|
Re: Replication lag due to lagging restart_lsn | milist ujang | 10:41 |
Postgres Metrics | André Rodrigues | 11:04 |
Re: Postgres Metrics | Joe Conway | 14:53 |
Thread | Author | Time |
---|---|---|
speeding up grafana sensor-data query on raspberry pi 3 | Clemens Eisserer | 17:00 |
Re: speeding up grafana sensor-data query on raspberry pi 3 | Justin Pryzby | 17:15 |
Re: speeding up grafana sensor-data query on raspberry pi 3 | David Rowley | 20:50 |
Re: speeding up grafana sensor-data query on raspberry pi 3 | Andres Freund | 22:10 |
Thread | Author | Time |
---|---|---|
Re: speeding up grafana sensor-data query on raspberry pi 3 | Luiz Felipph | 19:06 |
Thread | Author | Time |
---|---|---|
Re: time sorted UUIDs | peter plachta | 00:25 |
High QPS, random index writes and vacuum | peter plachta | 00:35 |
Re: High QPS, random index writes and vacuum | Peter Geoghegan | 00:38 |
Re: High QPS, random index writes and vacuum | Tom Lane | 02:01 |
Re: High QPS, random index writes and vacuum | David Rowley | 02:40 |
Re: High QPS, random index writes and vacuum | peter plachta | 02:43 |
Re: High QPS, random index writes and vacuum | peter plachta | 02:44 |
Re: High QPS, random index writes and vacuum | Thomas Munro | 02:49 |
Re: High QPS, random index writes and vacuum | Peter Geoghegan | 02:52 |
Re: speeding up grafana sensor-data query on raspberry pi 3 | Clemens Eisserer | 12:14 |
Thread | Author | Time |
---|---|---|
What is equivalent of v$sesstat and v$sql_plan in postgres? | kunwar singh | 13:37 |
Re: What is equivalent of v$sesstat and v$sql_plan in postgres? | MichaelDBA | 13:40 |
Re: speeding up grafana sensor-data query on raspberry pi 3 | Clemens Eisserer | 16:39 |
Thread | Author | Time |
---|---|---|
How do Monitoring tools capture explain plan of a query | kunwar singh | 15:28 |
Re: How do Monitoring tools capture explain plan of a query | kyle Hailey | 16:17 |
Thread | Author | Time |
---|---|---|
Re: How do Monitoring tools capture explain plan of a query | kunwar singh | 19:28 |
Thread | Author | Time |
---|---|---|
Re: Postgres Metrics | Jesper Pedersen | 08:23 |
Thread | Author | Time |
---|---|---|
Performance issues in query with multiple joins | Παρασκευη Πασσαρη | 12:19 |
Performance issues in query with multiple joins | David G. Johnston | 13:03 |
Re: Performance issues in query with multiple joins | Tom Lane | 14:07 |
Thread | Author | Time |
---|---|---|
Re: Performance issues in query with multiple joins | Laurenz Albe | 04:15 |
Thread | Author | Time |
---|---|---|
Fsync IO issue | ProfiVPS Support | 17:31 |
Re: Fsync IO issue | ProfiVPS Support | 17:41 |
Re: Fsync IO issue | Andres Freund | 19:21 |
Re: Fsync IO issue | ProfiVPS Support | 20:37 |
Re: Fsync IO issue | Thomas Munro | 21:23 |
Thread | Author | Time |
---|---|---|
Connection drops on postgres 11.16 | aditya desai | 18:40 |
Thread | Author | Time |
---|---|---|
PostgreSQL performance on ARM i.MX6 | Druckenmueller, Marc | 11:42 |
Re: PostgreSQL performance on ARM i.MX6 | Daniele Varrazzo | 13:25 |
Re: PostgreSQL performance on ARM i.MX6 | Tom Lane | 16:29 |
Re: PostgreSQL performance on ARM i.MX6 | Richard Huxton | 19:46 |
Re: PostgreSQL performance on ARM i.MX6 | Ranier Vilela | 19:56 |
Thread | Author | Time |
---|---|---|
Re: Fsync IO issue | Merlin Moncure | 20:56 |
Thread | Author | Time |
---|---|---|
Unaccounted regression from postgresql 11 in later versions | Bob Jolliffe | 08:43 |
Re: Unaccounted regression from postgresql 11 in later versions | Michael Christofides | 10:11 |
Re: Unaccounted regression from postgresql 11 in later versions | Bob Jolliffe | 10:26 |
How to reduce latency with fast short queries in Postgresql 15.3 on a NUMA server | Sergio Rus | 12:40 |
Re: How to reduce latency with fast short queries in Postgresql 15.3 on a NUMA server | Kenneth Marshall | 13:47 |
Re: How to reduce latency with fast short queries in Postgresql 15.3 on a NUMA server | Sergio Rus | 16:03 |
Re: How to reduce latency with fast short queries in Postgresql 15.3 on a NUMA server | Imre Samu | 17:17 |
Re: How to reduce latency with fast short queries in Postgresql 15.3 on a NUMA server | Andres Freund | 17:54 |
Re: How to reduce latency with fast short queries in Postgresql 15.3 on a NUMA server | Ranier Vilela | 18:16 |
Thread | Author | Time |
---|---|---|
thousands of CachedPlan entry per backend 📎 | James Pang (chaolpan) | 03:36 |
Re: thousands of CachedPlan entry per backend | Laurenz Albe | 06:53 |
Re: thousands of CachedPlan entry per backend | Pavel Stehule | 07:18 |
RE: thousands of CachedPlan entry per backend | James Pang (chaolpan) | 08:50 |
Re: thousands of CachedPlan entry per backend | Laurenz Albe | 12:48 |
Re: How to reduce latency with fast short queries in Postgresql 15.3 on a NUMA server | Sergio Rus | 14:26 |
Thread | Author | Time |
---|---|---|
RE: thousands of CachedPlan entry per backend | James Pang (chaolpan) | 01:45 |
Re: thousands of CachedPlan entry per backend | Pavel Stehule | 04:56 |
RE: thousands of CachedPlan entry per backend | James Pang (chaolpan) | 09:06 |
Re: thousands of CachedPlan entry per backend | Jeff Janes | 19:17 |
Thread | Author | Time |
---|---|---|
Understand time taken by individual SQL statements in a procedure | Satalabaha Postgres | 07:18 |
Re: Understand time taken by individual SQL statements in a procedure | Julien Rouhaud | 07:36 |
Re: Understand time taken by individual SQL statements in a procedure | Satalabaha Postgres | 17:46 |
Thread | Author | Time |
---|---|---|
Weird behavior of INSERT QUERY | Satalabaha Postgres | 08:34 |
Re: Weird behavior of INSERT QUERY | Satalabaha Postgres | 08:40 |
Re: Weird behavior of INSERT QUERY | Julien Rouhaud | 11:21 |
Re: Weird behavior of INSERT QUERY | Satalabaha Postgres | 11:42 |
Re: Weird behavior of INSERT QUERY | Julien Rouhaud | 13:21 |
Re: Weird behavior of INSERT QUERY | Tom Lane | 13:26 |
Re: Weird behavior of INSERT QUERY | Ranier Vilela | 14:16 |
Re: Weird behavior of INSERT QUERY | Satalabaha Postgres | 14:49 |
Re: Weird behavior of INSERT QUERY | Satalabaha Postgres | 14:58 |
Re: Weird behavior of INSERT QUERY | Ranier Vilela | 23:05 |
Thread | Author | Time |
---|---|---|
Re: Weird behavior of INSERT QUERY | Satalabaha Postgres | 11:55 |
Thread | Author | Time |
---|---|---|
wrong rows estimation by hash join | James Pang (chaolpan) | 08:36 |
Thread | Author | Time |
---|---|---|
Re: wrong rows estimation by hash join | Tomas Vondra | 20:38 |
Thread | Author | Time |
---|---|---|
Postgresql equal join on function with columns not use index | James Pang (chaolpan) | 08:09 |
Re: Postgresql equal join on function with columns not use index | Tom Lane | 13:18 |
RE: Postgresql equal join on function with columns not use index | James Pang (chaolpan) | 14:20 |
Forced to use UNION ALL when having multiple ANY operators and ORDER BY LIMIT | benoit | 20:17 |
Re: Forced to use UNION ALL when having multiple ANY operators and ORDER BY LIMIT | Peter Geoghegan | 20:34 |
RE: Forced to use UNION ALL when having multiple ANY operators and ORDER BY LIMIT | benoit | 20:50 |
Re: Forced to use UNION ALL when having multiple ANY operators and ORDER BY LIMIT | Chris Hoover | 20:55 |
RE: Forced to use UNION ALL when having multiple ANY operators and ORDER BY LIMIT | benoit | 21:34 |
Thread | Author | Time |
---|---|---|
Re: Helping planner to chose sequential scan when it improves performance | Ruslan Zakirov | 23:00 |
Thread | Author | Time |
---|---|---|
RE: Postgresql equal join on function with columns not use index | James Pang (chaolpan) | 08:32 |
Re: Postgresql equal join on function with columns not use index | Pavel Stehule | 08:35 |
Thread | Author | Time |
---|---|---|
Merge David and Goliath tables efficiently | Nicolas Paris | 13:48 |
Re: Merge David and Goliath tables efficiently | Tomas Vondra | 19:52 |
Re: Merge David and Goliath tables efficiently | nicolas paris | 21:42 |
Re: Merge David and Goliath tables efficiently | Tomas Vondra | 23:48 |
Thread | Author | Time |
---|---|---|
Re: Merge David and Goliath tables efficiently | nicolas paris | 20:57 |
RE: Forced to use UNION ALL when having multiple ANY operators and ORDER BY LIMIT | msalais | 21:23 |
Thread | Author | Time |
---|---|---|
Re: Merge David and Goliath tables efficiently | Alvaro Herrera | 07:46 |
Re: Merge David and Goliath tables efficiently | Tomas Vondra | 11:34 |
Re: Merge David and Goliath tables efficiently 📎 | Tomas Vondra | 11:53 |
Re: Merge David and Goliath tables efficiently | nicolas paris | 12:09 |
Re: Merge David and Goliath tables efficiently | nicolas paris | 12:20 |
Re: Merge David and Goliath tables efficiently | Tomas Vondra | 13:13 |
Re: Merge David and Goliath tables efficiently 📎 | nicolas paris | 15:45 |
Re: Forced to use UNION ALL when having multiple ANY operators and ORDER BY LIMIT | Benoit Tigeot | 16:30 |
Index on (fixed size) bytea value | Les | 20:05 |
Re: Index on (fixed size) bytea value | David G. Johnston | 20:30 |
Re: Merge David and Goliath tables efficiently | Tomas Vondra | 23:25 |
Thread | Author | Time |
---|---|---|
Re: Index on (fixed size) bytea value | Les | 06:13 |
Re: Index on (fixed size) bytea value | Laurenz Albe | 06:50 |
Re: Index on (fixed size) bytea value | Les | 07:18 |
Re: Merge David and Goliath tables efficiently | nicolas paris | 10:02 |
Re: Merge David and Goliath tables efficiently | Tomas Vondra | 12:45 |
Thread | Author | Time |
---|---|---|
Re: extended statistics n-distinct on multiple columns not used when join two tables | David Rowley | 00:53 |
Thread | Author | Time |
---|---|---|
Fwd: Helping planner to chose sequential scan when it improves performance 📎 | Patrick O'Toole | 06:29 |
Re: Helping planner to chose sequential scan when it improves performance | Jeff Janes | 19:34 |
Re: Helping planner to chose sequential scan when it improves performance | David Rowley | 19:48 |
Thread | Author | Time |
---|---|---|
Re: Helping planner to chose sequential scan when it improves performance | Jeff Janes | 12:47 |
Thread | Author | Time |
---|---|---|
Why is query performance on RLS enabled Postgres worse? | Akash Anand | 06:03 |
Re: Why is query performance on RLS enabled Postgres worse? | Akash Anand | 07:01 |
Performance implications of 8K pread()s | Dimitrios Apostolou | 14:28 |
Thread | Author | Time |
---|---|---|
Entire index scanned, but only when in SQL function? | Philip Semanchuk | 16:07 |
Re: Performance implications of 8K pread()s | Thomas Munro | 17:12 |
Re: Performance implications of 8K pread()s | Thomas Munro | 17:22 |
Thread | Author | Time |
---|---|---|
Re: Performance implications of 8K pread()s | Dimitrios Apostolou | 18:50 |
Thread | Author | Time |
---|---|---|
Re: Performance implications of 8K pread()s | Thomas Munro | 22:32 |
Thread | Author | Time |
---|---|---|
Re: Performance implications of 8K pread()s | Dimitrios Apostolou | 14:42 |
Re: Performance implications of 8K pread()s | Andres Freund | 15:34 |
Thread | Author | Time |
---|---|---|
TOAST Fields serialisation/deserialization performance | Piyush Katariya | 12:45 |
Re: TOAST Fields serialisation/deserialization performance | Laurenz Albe | 19:39 |
Re: TOAST Fields serialisation/deserialization performance | Piyush Katariya | 19:48 |
Thread | Author | Time |
---|---|---|
Results of experiments with UUIDv7, UUIDv8 | peter plachta | 04:48 |
Table copy with SERIALIZABLE is incredibly slow | peter plachta | 05:00 |
Re: Table copy with SERIALIZABLE is incredibly slow | Laurenz Albe | 06:30 |
Thread | Author | Time |
---|---|---|
Plan weirdness. A sort produces more rows than the node beneath it | Dane Foster | 14:59 |
Re: Plan weirdness. A sort produces more rows than the node beneath it | Jeff Janes | 15:07 |
Re: Plan weirdness. A sort produces more rows than the node beneath it | Dane Foster | 15:09 |
Re: Plan weirdness. A sort produces more rows than the node beneath it | Tom Lane | 15:10 |
Re: Plan weirdness. A sort produces more rows than the node beneath it | Dane Foster | 15:15 |
Re: Plan weirdness. A sort produces more rows than the node beneath it | Tom Lane | 15:31 |
Re: Plan weirdness. A sort produces more rows than the node beneath it | Dane Foster | 16:41 |
Thread | Author | Time |
---|---|---|
Function call very slow from JDBC/java but super fast from DBear | An, Hongguo (CORP) | 23:07 |
Thread | Author | Time |
---|---|---|
Re: Function call very slow from JDBC/java but super fast from DBear | Dave Cramer | 13:29 |
Re: Function call very slow from JDBC/java but super fast from DBear | An, Hongguo (CORP) | 16:50 |
Thread | Author | Time |
---|---|---|
Re: Function call very slow from JDBC/java but super fast from DBear | David G. Johnston | 03:33 |
Partitioning update-heavy queue with hash partitions vs partial indexes | Dorian Hoxha | 08:36 |
Thread | Author | Time |
---|---|---|
Re: Partitioning update-heavy queue with hash partitions vs partial indexes | David Rowley | 04:49 |
Re: Partitioning update-heavy queue with hash partitions vs partial indexes | burcinyazici | 05:13 |
Re: Partitioning update-heavy queue with hash partitions vs partial indexes | Dorian Hoxha | 11:09 |
Thread | Author | Time |
---|---|---|
slow delete | Les | 20:23 |
Re: slow delete | Tom Lane | 20:37 |
Thread | Author | Time |
---|---|---|
Re: slow delete | Les | 04:43 |
Re: slow delete | Jeff Janes | 14:03 |
Thread | Author | Time |
---|---|---|
Question regarding writes when locking rows | Martin Querleu | 09:19 |
Thread | Author | Time |
---|---|---|
Slow query, possibly not using index | Les | 11:58 |
Re: Slow query, possibly not using index | Tom Lane | 13:27 |
Re: Slow query, possibly not using index | Les | 17:39 |
Re: Slow query, possibly not using index | Wael Khobalatte | 18:54 |
Re: Slow query, possibly not using index | Tom Lane | 23:34 |
Thread | Author | Time |
---|---|---|
Re: Slow query, possibly not using index | Les | 06:04 |
Re: Slow query, possibly not using index | Les | 07:21 |
Re: Slow query, possibly not using index | Les | 10:59 |
Re: Slow query, possibly not using index | Pavel Stehule | 11:03 |
Re: Slow query, possibly not using index | David Rowley | 11:42 |
Re: Slow query, possibly not using index | Les | 11:47 |
Thread | Author | Time |
---|---|---|
Index bloat and REINDEX/VACUUM optimization for partial index | jayaprabhakar k | 00:32 |
Re: Index bloat and REINDEX/VACUUM optimization for partial index | Peter Geoghegan | 01:49 |