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: Bad plan chosen for union all | Alex Reece | 03:39 |
Re: Bad plan chosen for union all | Tom Lane | 04:43 |
Re: Bad plan chosen for union all | Alex Reece | 05:31 |
ODBC--call failed :: Bindings were not allocated properly | Dinesh Chandra 12108 | 14:47 |
Thread | Author | Time |
---|---|---|
CREATE TABLE vs CREATE MATERIALIZED VIEW | Caio Guimarães Figueiredo | 12:07 |
Thread | Author | Time |
---|---|---|
Delete tables difference involves seq scan | Danylo Hlynskyi | 13:03 |
Re: Delete tables difference involves seq scan | Danylo Hlynskyi | 13:17 |
Re: Delete tables difference involves seq scan | Danylo Hlynskyi | 14:52 |
Bad plan for ltree predicate <@ | Roman Konoval | 17:20 |
Bitmap scan is undercosted? | Vitaliy Garnashevich | 17:40 |
Re: Bitmap scan is undercosted? | Justin Pryzby | 18:34 |
Re: Bad plan for ltree predicate <@ | Tom Lane | 21:33 |
Re: Bitmap scan is undercosted? | Vitaliy Garnashevich | 23:08 |
Re: Bitmap scan is undercosted? | Justin Pryzby | 23:11 |
Re: Bitmap scan is undercosted? | Vitaliy Garnashevich | 23:54 |
Thread | Author | Time |
---|---|---|
Re: Bitmap scan is undercosted? | Justin Pryzby | 02:06 |
Re: Bad plan for ltree predicate <@ | Roman Konoval | 02:34 |
Re: Bitmap scan is undercosted? | Jeff Janes | 05:51 |
Re: Bitmap scan is undercosted? | Justin Pryzby | 06:41 |
Re: Bitmap scan is undercosted? | Vitaliy Garnashevich | 07:08 |
Re: Bitmap scan is undercosted? | Jeff Janes | 21:17 |
Re: Bitmap scan is undercosted? | Tom Lane | 23:44 |
Thread | Author | Time |
---|---|---|
Re: Bitmap scan is undercosted? | Jeff Janes | 01:27 |
Re: Bitmap scan is undercosted? - boolean correlation | Justin Pryzby | 04:04 |
Re: Bitmap scan is undercosted? | Vitaliy Garnashevich | 21:15 |
Re: Bitmap scan is undercosted? | Vitaliy Garnashevich | 21:22 |
Re: Bitmap scan is undercosted? | Vitaliy Garnashevich | 22:11 |
Re: Bitmap scan is undercosted? 📎 | Tom Lane | 23:08 |
Re: Bitmap scan is undercosted? - boolean correlation | Jeff Janes | 23:21 |
Re: Bitmap scan is undercosted? - boolean correlation | Tom Lane | 23:31 |
Thread | Author | Time |
---|---|---|
Re: Bitmap scan is undercosted? - boolean correlation | Jeff Janes | 00:27 |
Thread | Author | Time |
---|---|---|
Re: Half billion records in one table? RDS | Aaron Werman | 01:59 |
Re: insert and query performance on big string table with pg_trgm | Matthew Hall | 06:15 |
Re: Bitmap scan is undercosted? 📎 | Vitaliy Garnashevich | 07:06 |
Re: insert and query performance on big string table with pg_trgm | Sergei Kornilov | 07:23 |
Re: Different plan chosen when in lateral subquery | Laurenz Albe | 08:20 |
Re: Bitmap scan is undercosted? - overestimated correlation and cost_index | Justin Pryzby | 21:46 |
Thread | Author | Time |
---|---|---|
Re: Bitmap scan is undercosted? | Vitaliy Garnashevich | 00:17 |
Re: insert and query performance on big string table with pg_trgm | Matthew Hall | 02:04 |
Re: Bitmap scan is undercosted? | Jeff Janes | 03:48 |
Re: Bitmap scan is undercosted? - boolean correlation 📎 | Jeff Janes | 04:51 |
Re: pg_dump 3 times as slow after 8.4 -> 9.5 upgrade | Gunther | 12:46 |
Re: [PERFORM] Slow execution of SET ROLE, SET search_path and RESET ROLE | Ulf Lohbrügge | 12:54 |
Re: [PERFORM] Slow execution of SET ROLE, SET search_path and RESET ROLE | Tom Lane | 16:01 |
Re: [PERFORM] Slow execution of SET ROLE, SET search_path and RESET ROLE | Ulf Lohbrügge | 16:15 |
Re: [PERFORM] Slow execution of SET ROLE, SET search_path and RESET ROLE | Tom Lane | 16:38 |
Re: pg_dump 3 times as slow after 8.4 -> 9.5 upgrade | Laurenz Albe | 17:31 |
Re: pg_dump 3 times as slow after 8.4 -> 9.5 upgrade | Claudio Freire | 17:56 |
Thread | Author | Time |
---|---|---|
Learning EXPLAIN | Flávio Henrique | 01:12 |
Table with large number of int columns, very slow COPY FROM | Alex Tokarev | 04:21 |
Re: Setting effective_io_concurrency in VM? | Mark Kirkwood | 04:51 |
Re: Table with large number of int columns, very slow COPY FROM | Andreas Kretschmer | 07:20 |
Re: Learning EXPLAIN | Guillaume Lelarge | 13:20 |
Re: Learning EXPLAIN | Flavio Henrique Araque Gurgel | 13:32 |
Re: Learning EXPLAIN | Gustavo Velasquez | 16:44 |
Re: Table with large number of int columns, very slow COPY FROM | Andres Freund | 18:17 |
Faster str to int conversion (was Table with large number of int columns, very slow COPY FROM) 📎 | Andres Freund | 21:44 |
Thread | Author | Time |
---|---|---|
Re: Learning EXPLAIN | Sam Gendler | 04:47 |
Re: Learning EXPLAIN | Sam Gendler | 04:52 |
Thread | Author | Time |
---|---|---|
Prepared Transactions | Riaan Stander | 00:39 |
Re: Prepared Transactions | Sergei Kornilov | 08:14 |
Re: Prepared Transactions | jwhiting | 12:13 |
Thread | Author | Time |
---|---|---|
Re: Bitmap scan is undercosted? | Jeff Janes | 07:29 |
Re: Bitmap scan is undercosted? - overestimated correlation and cost_index | Jeff Janes | 09:29 |
PostgreSQL database size is not reasonable | Mariel Cherkassky | 15:15 |
Re: PostgreSQL database size is not reasonable | David G. Johnston | 15:21 |
RE: PostgreSQL database size is not reasonable | Craig McIlwee | 15:44 |
Re: PostgreSQL database size is not reasonable | Tom Lane | 15:49 |
Re: PostgreSQL database size is not reasonable | Mariel Cherkassky | 16:22 |
Re: PostgreSQL database size is not reasonable | Tom Lane | 17:59 |
Thread | Author | Time |
---|---|---|
CPU 100% usage caused by unknown postgres process.. | Dinesh Chandra 12108 | 10:12 |
Re: CPU 100% usage caused by unknown postgres process.. | Laurenz Albe | 10:36 |
Re: CPU 100% usage caused by unknown postgres process.. | Justin Pryzby | 12:19 |
Re: CPU 100% usage caused by unknown postgres process.. | Tomas Vondra | 15:22 |
Thread | Author | Time |
---|---|---|
Re: Bitmap scan is undercosted? - overestimated correlation and cost_index | Justin Pryzby | 20:54 |
Thread | Author | Time |
---|---|---|
Re: Bitmap scan is undercosted? - overestimated correlation and cost_index | Justin Pryzby | 19:18 |
Thread | Author | Time |
---|---|---|
Re: Bitmap scan is undercosted? - overestimated correlation and cost_index | Justin Pryzby | 02:37 |
Thread | Author | Time |
---|---|---|
WHERE IN for JOIN subquery? | Dave Johansen | 00:00 |
Re: WHERE IN for JOIN subquery? | David G. Johnston | 00:10 |
Re: WHERE IN for JOIN subquery? | Dave Johansen | 00:29 |
Autoanalyze CPU usage | Habib Nahas | 16:47 |
Re: Autoanalyze CPU usage | Justin Pryzby | 17:09 |
Re: Autoanalyze CPU usage | Tomas Vondra | 22:03 |
Re: Autoanalyze CPU usage | Habib Nahas | 22:53 |
Re: Autoanalyze CPU usage | Habib Nahas | 22:53 |
Re: Autoanalyze CPU usage | Justin Pryzby | 22:55 |
Thread | Author | Time |
---|---|---|
Re: Autoanalyze CPU usage | Michaeldba@sqlexec.com | 01:10 |
Re: Autoanalyze CPU usage | Laurenz Albe | 07:15 |
Re: Autoanalyze CPU usage | Nikolay Samokhvalov | 08:24 |
Re: Autoanalyze CPU usage | Habib Nahas | 14:38 |
Thread | Author | Time |
---|---|---|
Updating a large table | Timokhin Maxim | 16:46 |
Thread | Author | Time |
---|---|---|
Re: Updating a large table | salah jubeh | 11:31 |
Re: Updating a large table | Tomas Vondra | 20:58 |
Thread | Author | Time |
---|---|---|
Batch insert heavily affecting query performance. | Jean Baro | 19:51 |
Re: Batch insert heavily affecting query performance. | MichaelDBA@sqlexec.com | 23:52 |
Thread | Author | Time |
---|---|---|
Re: Batch insert heavily affecting query performance. | Jean Baro | 00:09 |
Re: Batch insert heavily affecting query performance. | MichaelDBA | 01:30 |
Re: Batch insert heavily affecting query performance. | Danylo Hlynskyi | 02:59 |
Re: Batch insert heavily affecting query performance. | Jean Baro | 03:10 |
Thread | Author | Time |
---|---|---|
Re: Batch insert heavily affecting query performance. | Jean Baro | 15:13 |
Re: Batch insert heavily affecting query performance. | Rick Otten | 15:38 |
RE: Batch insert heavily affecting query performance. | Mike Sofen | 15:58 |
Re: Batch insert heavily affecting query performance. | Jeremy Finzel | 16:02 |
Re: Batch insert heavily affecting query performance. | Jean Baro | 16:23 |
Re: Batch insert heavily affecting query performance. | Jeff Janes | 16:23 |
Re: Batch insert heavily affecting query performance. | Jean Baro | 16:34 |
RE: Batch insert heavily affecting query performance. | Jean Baro | 16:36 |
Re: Batch insert heavily affecting query performance. | Jean Baro | 16:37 |
Re: Batch insert heavily affecting query performance. | Jean Baro | 17:02 |
Re: Batch insert heavily affecting query performance. | Alvaro Hernandez | 17:09 |
RE: Batch insert heavily affecting query performance. | Mike Sofen | 17:10 |
Re: Batch insert heavily affecting query performance. | David Miller | 17:15 |
Thread | Author | Time |
---|---|---|
Table performance with millions of rows | Robert Blayzor | 00:54 |
Re: Table performance with millions of rows (partitioning) | Justin Pryzby | 01:20 |
Re: Table performance with millions of rows (partitioning) | Robert Blayzor | 01:27 |
Re: Table performance with millions of rows (partitioning) | pinker | 02:22 |
Thread | Author | Time |
---|---|---|
partitioning an existing table | Robert Blayzor | 04:37 |
Re: partitioning an existing table | Justin Pryzby | 05:38 |
analyze stats: child vs parent | Justin Pryzby | 05:56 |
Re: partitioning an existing table | Robert Blayzor | 14:19 |
Re: partitioning an existing table - efficient pg_dump | Justin Pryzby | 18:42 |
Thread | Author | Time |
---|---|---|
Restoring a table is ten times slower on Ubuntu 14.04 than on Ubuntu 16.04 | Hans Braxmeier | 13:27 |
Re: Restoring a table is ten times slower on Ubuntu 14.04 than on Ubuntu 16.04 | Vasilis Ventirozos | 13:30 |
primary key hash index | Rick Otten | 14:02 |
Re: primary key hash index | Magnus Hagander | 14:09 |
Thread | Author | Time |
---|---|---|
Re: primary key hash index | Jeff Janes | 20:01 |
Thread | Author | Time |
---|---|---|
GEQO and join_collapse_limit correlation 📎 | Juan José Santamaría Flecha | 14:30 |
Re: GEQO and join_collapse_limit correlation | Tom Lane | 16:16 |
Re: GEQO and join_collapse_limit correlation | Juan José Santamaría Flecha | 20:17 |
Re: GEQO and join_collapse_limit correlation | Tom Lane | 20:29 |
Thread | Author | Time |
---|---|---|
Re: GEQO and join_collapse_limit correlation | Juan José Santamaría Flecha | 11:31 |
Thread | Author | Time |
---|---|---|
seeing lag in postgresql replication | Rambabu V | 09:21 |
Re: seeing lag in postgresql replication | Mariel Cherkassky | 10:31 |
Thread | Author | Time |
---|---|---|
Need Help on wal_compression | Rambabu V | 06:53 |
Re: Updating a large table | Timokhin Maxim | 12:18 |
Re: Updating a large table | Sergei Kornilov | 12:53 |
Re: Updating a large table | Timokhin Maxim | 16:31 |
Re: Need Help on wal_compression | Claudio Freire | 16:53 |
Re: Batch insert heavily affecting query performance. | Claudio Freire | 19:45 |
Re: Need Help on wal_compression | Scott Marlowe | 20:39 |
Performance of a Query 📎 | Kumar, Virendra | 21:18 |
View preformance oracle to postgresql | Reddygari, Pavan | 21:32 |
Re: Need Help on wal_compression | Jeff Janes | 21:33 |
Re: Performance of a Query | Scott Marlowe | 22:08 |
RE: Performance of a Query | Kumar, Virendra | 22:25 |
PG 9.5 2 tables same DDL with diff size | ghiureai | 22:54 |
Re: Performance of a Query | Scott Marlowe | 22:59 |
RE: Performance of a Query 📎 | Kumar, Virendra | 23:09 |
Re: Performance of a Query | Scott Marlowe | 23:25 |
Thread | Author | Time |
---|---|---|
Slow queries after Windows startup | POUSSEL, Guillaume | 08:19 |
Re: Slow queries after Windows startup | Robert Zenz | 09:01 |
RE: Slow queries after Windows startup | POUSSEL, Guillaume | 09:06 |
Re: Slow queries after Windows startup | Robert Zenz | 09:54 |
RE: Slow queries after Windows startup | POUSSEL, Guillaume | 13:36 |
Disjunctions and sequential scans 📎 | Ronuk Raval | 16:30 |
RE: Slow queries after Windows startup | Éric Fontaine | 21:08 |
Thread | Author | Time |
---|---|---|
PGadmin error while connecting with database. | Dinesh Chandra 12108 | 04:55 |
Re: Query is slow when run for first time; subsequent execution is fast | Nandakumar M | 08:03 |
Re: PGadmin error while connecting with database. | Mariel Cherkassky | 08:44 |
Re: Query is slow when run for first time; subsequent execution is fast | Pavel Stehule | 10:04 |
Thread | Author | Time |
---|---|---|
Re: Re: PGadmin error while connecting with database. | Dinesh Chandra 12108 | 04:10 |
HDD vs SSD without explanation | Neto pr | 20:44 |
Re: HDD vs SSD without explanation | Justin Pryzby | 21:40 |
Re: HDD vs SSD without explanation | Neto pr | 23:59 |
Thread | Author | Time |
---|---|---|
Re: HDD vs SSD without explanation | Neto pr | 02:25 |
Re: HDD vs SSD without explanation | Neto pr | 02:36 |
Re: HDD vs SSD without explanation | Justin Pryzby | 03:09 |
Re: HDD vs SSD without explanation | Neto pr | 11:04 |
Re: HDD vs SSD without explanation | Neto pr | 12:35 |
Re: HDD vs SSD without explanation | Georg H. | 18:32 |