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: Slow Running Queries in Azure PostgreSQL | Kumar, Mukesh | 12:41 |
Re: An I/O error occurred while sending to the backend (PG 13.4) | Justin Pryzby | 13:02 |
slow query to improve performace 📎 | Ayub Khan | 20:18 |
Re: slow query to improve performace | Justin Pryzby | 22:52 |
Thread | Author | Time |
---|---|---|
Never Ending query in PostgreSQL 📎 | Kumar, Mukesh | 04:40 |
Re: Never Ending query in PostgreSQL | Julien Rouhaud | 12:22 |
Re: Never Ending query in PostgreSQL | Jeff Janes | 17:20 |
Thread | Author | Time |
---|---|---|
Re: slow query to improve performace | Jeff Janes | 03:18 |
RE: An I/O error occurred while sending to the backend (PG 13.4) | ldh@laurent-hasson.com | 16:50 |
RE: An I/O error occurred while sending to the backend (PG 13.4) | ldh@laurent-hasson.com | 21:43 |
Re: An I/O error occurred while sending to the backend (PG 13.4) | Justin Pryzby | 22:05 |
RLS not using index scan but seq scan when condition gets a bit complicated | Charles Huang | 23:33 |
Thread | Author | Time |
---|---|---|
Re: An I/O error occurred while sending to the backend (PG 13.4) | Ranier Vilela | 01:15 |
Re: Advice needed: query performance deteriorates by 2000% within 1 minute | Michael Lewis | 01:39 |
Re: Advice needed: query performance deteriorates by 2000% within 1 minute | Michael Lewis | 01:44 |
RE: Simple task with partitioning which I can't realize | Michel SALAIS | 07:28 |
Re: Simple task with partitioning which I can't realize | Geri Wright | 12:14 |
Re: Simple task with partitioning which I can't realize | Mladen Gogala | 14:04 |
Thread | Author | Time |
---|---|---|
OOM killer while pg_restore | Marc Rechté | 08:59 |
Re: OOM killer while pg_restore | Ranier Vilela | 11:00 |
Re: OOM killer while pg_restore | Marc Rechté | 12:18 |
Re: OOM killer while pg_restore | Ranier Vilela | 12:22 |
Re: OOM killer while pg_restore | Justin Pryzby | 14:46 |
RE: An I/O error occurred while sending to the backend (PG 13.4) | ldh@laurent-hasson.com | 14:55 |
Re: OOM killer while pg_restore | Tom Lane | 15:31 |
Re: An I/O error occurred while sending to the backend (PG 13.4) | Ranier Vilela | 16:33 |
Re: An I/O error occurred while sending to the backend (PG 13.4) | Justin Pryzby | 16:46 |
Re: An I/O error occurred while sending to the backend (PG 13.4) | Ranier Vilela | 16:56 |
RE: An I/O error occurred while sending to the backend (PG 13.4) | ldh@laurent-hasson.com | 18:19 |
Re: An I/O error occurred while sending to the backend (PG 13.4) | Ranier Vilela | 18:22 |
Re: OOM killer while pg_restore | Marc Rechté | 18:32 |
Re: OOM killer while pg_restore | Tom Lane | 18:43 |
Thread | Author | Time |
---|---|---|
Any way to speed up INSERT INTO | aditya desai | 18:31 |
Re: Any way to speed up INSERT INTO | Bruce Momjian | 18:38 |
Re: Any way to speed up INSERT INTO | Tom Lane | 18:42 |
Re: Any way to speed up INSERT INTO | aditya desai | 18:42 |
Re: Any way to speed up INSERT INTO | Bruce Momjian | 18:47 |
Re: Any way to speed up INSERT INTO | Andres Freund | 18:52 |
RES: Any way to speed up INSERT INTO | Edson Richter | 20:04 |
Thread | Author | Time |
---|---|---|
Re: Any way to speed up INSERT INTO | Imre Samu | 01:22 |
XA transactions much slower on 14.2 than on 13.5 | Mladen Gogala | 02:33 |
Re: XA transactions much slower on 14.2 than on 13.5 | Tom Lane | 02:44 |
Re: Any way to speed up INSERT INTO | aditya desai | 07:02 |
Re: OOM killer while pg_restore | Marc Rechté | 08:56 |
Re: OOM killer while pg_restore | Ranier Vilela | 12:08 |
Thread | Author | Time |
---|---|---|
Optimal configuration for server | Luiz Felipph | 11:51 |
Re: Optimal configuration for server | Ranier Vilela | 16:51 |
Re: Optimal configuration for server | Luiz Felipph | 17:17 |
Re: Optimal configuration for server | Ranier Vilela | 17:39 |
Re: Optimal configuration for server | Tomas Vondra | 18:07 |
Re: Optimal configuration for server | Luiz Felipph | 21:07 |
Re: Optimal configuration for server | Ranier Vilela | 22:28 |
Thread | Author | Time |
---|---|---|
Re: Optimal configuration for server | Justin Pryzby | 06:44 |
Re: Any way to speed up INSERT INTO | aditya desai | 13:06 |
Re: Any way to speed up INSERT INTO | Bruce Momjian | 14:53 |
Thread | Author | Time |
---|---|---|
Re: Any way to speed up INSERT INTO | aditya desai | 06:09 |
Thread | Author | Time |
---|---|---|
Explain analyse with track_io_timing | Jayadevan M | 05:10 |
Re: Explain analyse with track_io_timing | Julien Rouhaud | 06:05 |
Re: Explain analyse with track_io_timing | Jayadevan M | 06:10 |
Thread | Author | Time |
---|---|---|
Re: Optimal configuration for server | Moises Lopez | 01:00 |
Thread | Author | Time |
---|---|---|
RE: Optimal configuration for server | Michel SALAIS | 14:01 |
Thread | Author | Time |
---|---|---|
Performance issue post upgrade on Version 13 - Incorrect Estimation Cost choosing Hash Aggregate-Nested Left Loop Join 📎 | Prajna Shetty | 12:57 |
Thread | Author | Time |
---|---|---|
Re: Using system tables directly takes many hours, using temp tables with no indexes takes a few seconds for geometry_columns view. | Lars Aksel Opsahl | 09:39 |
Re: Performance issue post upgrade on Version 13 - Incorrect Estimation Cost choosing Hash Aggregate-Nested Left Loop Join | Tomas Vondra | 11:55 |
Re: Performance issue post upgrade on Version 13 - Incorrect Estimation Cost choosing Hash Aggregate-Nested Left Loop Join | Justin Pryzby | 12:24 |
View taking time to show records | Kumar, Mukesh | 15:59 |
Thread | Author | Time |
---|---|---|
Re: View taking time to show records | aditya desai | 10:20 |
Re: View taking time to show records | hubert depesz lubaczewski | 10:39 |
Re: View taking time to show records | Laurenz Albe | 10:43 |
RE: View taking time to show records | Kumar, Mukesh | 14:07 |
Thread | Author | Time |
---|---|---|
Re: View taking time to show records | Laurenz Albe | 04:37 |
Thread | Author | Time |
---|---|---|
HIGH IO and Less CPU utilization | Rambabu g | 18:04 |
Re: HIGH IO and Less CPU utilization | Justin Pryzby | 18:24 |
Re: HIGH IO and Less CPU utilization | Rambabu g | 19:22 |
Re: HIGH IO and Less CPU utilization | Justin Pryzby | 19:39 |
Thread | Author | Time |
---|---|---|
Re: HIGH IO and Less CPU utilization | Rambabu g | 04:47 |
RE: High process memory consumption when running sort | Shai Shapira | 10:42 |
Thread | Author | Time |
---|---|---|
Re: HIGH IO and Less CPU utilization | Justin Pryzby | 06:49 |
Postgresql TPS Bottleneck | wakandavision | 11:50 |
Re: Postgresql TPS Bottleneck | Guillaume Cottenceau | 14:18 |
Re: HIGH IO and Less CPU utilization | Mladen Gogala | 14:44 |
Re: Postgresql TPS Bottleneck | MichaelDBA | 18:55 |
Re: Postgresql TPS Bottleneck | Tomas Vondra | 19:16 |
Thread | Author | Time |
---|---|---|
Re: Postgresql TPS Bottleneck | Mladen Gogala | 02:40 |
Thread | Author | Time |
---|---|---|
Re: HIGH IO and Less CPU utilization | Rambabu g | 07:47 |
Thread | Author | Time |
---|---|---|
Slow Planning Times | Saurabh Sehgal | 00:26 |
Re: Slow Planning Times | Saurabh Sehgal | 00:40 |
Re: Slow Planning Times | David G. Johnston | 00:54 |
Re: Slow Planning Times | Saurabh Sehgal | 01:47 |
Re: Slow Planning Times | Tom Lane | 02:57 |
Re: Slow Planning Times | Saurabh Sehgal | 04:09 |
Thread | Author | Time |
---|---|---|
Performance for SQL queries on Azure PostgreSQL PaaS instance | Kumar, Mukesh | 09:10 |
Re: Performance for SQL queries on Azure PostgreSQL PaaS instance | Frits Jalvingh | 14:23 |
Re: Performance for SQL queries on Azure PostgreSQL PaaS instance | Tomas Vondra | 15:06 |
Thread | Author | Time |
---|---|---|
Re: Performance for SQL queries on Azure PostgreSQL PaaS instance | Laurenz Albe | 08:34 |
RE: Performance for SQL queries on Azure PostgreSQL PaaS instance | Kumar, Mukesh | 08:42 |
Re: Performance for SQL queries on Azure PostgreSQL PaaS instance | andrew cooke | 11:17 |
RE: An I/O error occurred while sending to the backend (PG 13.4) | ldh@laurent-hasson.com | 15:36 |
Re: An I/O error occurred while sending to the backend (PG 13.4) | Justin Pryzby | 15:43 |
Thread | Author | Time |
---|---|---|
Query Tunning related to function 📎 | Kumar, Mukesh | 06:03 |
SQL performance issue after migration from Oracle to Aurora postgres | Goti | 09:35 |
Re: Query Tunning related to function | Ranier Vilela | 14:26 |
Re: SQL performance issue after migration from Oracle to Aurora postgres | Andrew Dunstan | 14:40 |
RE: Query Tunning related to function | Kumar, Mukesh | 14:44 |
RE: Query Tunning related to function | Michel SALAIS | 18:14 |
RE: Query Tunning related to function | Kumar, Mukesh | 18:45 |
Re: Performance for SQL queries on Azure PostgreSQL PaaS instance | overland | 20:20 |
Re: Query Tunning related to function | Bhupendra Babu | 22:13 |
Query Planner not taking advantage of HASH PARTITION | Benjamin Tingle | 23:36 |
Thread | Author | Time |
---|---|---|
RE: Query Tunning related to function 📎 | Kumar, Mukesh | 06:13 |
RE: Query Tunning related to function | Kumar, Mukesh | 16:46 |
Thread | Author | Time |
---|---|---|
Re: Query Tunning related to function | Justin Pryzby | 03:13 |
Re: Query Planner not taking advantage of HASH PARTITION | Tom Lane | 16:09 |
Re: Query Tunning related to function | David G. Johnston | 16:47 |
Re: Query Planner not taking advantage of HASH PARTITION | Benjamin Tingle | 17:07 |
Re: Query Planner not taking advantage of HASH PARTITION | Tom Lane | 18:20 |
Re: Query Planner not taking advantage of HASH PARTITION | Alvaro Herrera | 18:50 |
Thread | Author | Time |
---|---|---|
How to find the final transformed query in postgresql | Goti | 14:02 |
Re: How to find the final transformed query in postgresql | Tom Lane | 14:13 |
Re: How to find the final transformed query in postgresql | Goti | 14:31 |
Thread | Author | Time |
---|---|---|
How to find all SQLs executed by a transaction id? | Patil, Ravi | 12:35 |
significant jump in sql statement timing for on server vs a remote connection | Sbob | 21:00 |
Re: significant jump in sql statement timing for on server vs a remote connection | Justin Pryzby | 21:04 |
Thread | Author | Time |
---|---|---|
Re: significant jump in sql statement timing for on server vs a remote connection | Jeff Janes | 04:17 |
Re: Postgresql TPS Bottleneck | wakandavision | 06:49 |
Re: significant jump in sql statement timing for on server vs a remote connection | Sbob | 15:16 |
Re: Postgresql TPS Bottleneck 📎 | Jeff Janes | 15:49 |
Re: significant jump in sql statement timing for on server vs a remote connection | Ranier Vilela | 15:51 |
Re: Postgresql TPS Bottleneck | wakandavision | 16:35 |
Re: Postgresql TPS Bottleneck | Benedict Holland | 18:18 |
Thread | Author | Time |
---|---|---|
Re: Query Planner not taking advantage of HASH PARTITION | Benjamin Tingle | 02:11 |
Re: Query Planner not taking advantage of HASH PARTITION | Justin Pryzby | 11:52 |
Thread | Author | Time |
---|---|---|
Performance differential when 0 values present vs when 1 values present. Planner return 52k rows when 0 expected. | Emil Iggland | 14:53 |
Thread | Author | Time |
---|---|---|
Re: Performance differential when 0 values present vs when 1 values present. Planner return 52k rows when 0 expected. | Tom Lane | 16:00 |
Thread | Author | Time |
---|---|---|
Re: Performance differential when 0 values present vs when 1 values present. Planner return 52k rows when 0 expected. | Emil Iggland | 07:41 |
Thread | Author | Time |
---|---|---|
Re: Performance differential when 0 values present vs when 1 values present. Planner return 52k rows when 0 expected. | David Rowley | 08:22 |
Fwd: Array of integer indexed nested-loop semi join | Mickael van der Beek | 12:18 |
Re: Array of integer indexed nested-loop semi join | Jeff Janes | 14:28 |
Re: Array of integer indexed nested-loop semi join | Mickael van der Beek | 14:54 |
Thread | Author | Time |
---|---|---|
Unworkable plan above certain row count | André Hänsel | 00:52 |
Re: Unworkable plan above certain row count | Tom Lane | 02:08 |
Re: Performance differential when 0 values present vs when 1 values present. Planner return 52k rows when 0 expected. | Emil Iggland | 08:09 |
LISTEN NOTIFY sometimes huge delay | Peter Eser HEUFT [Germany] | 14:28 |
Re: LISTEN NOTIFY sometimes huge delay | Tom Lane | 16:38 |
Thread | Author | Time |
---|---|---|
FATAL: canceling authentication due to timeout | aditya desai | 10:59 |
Fwd: FATAL: canceling authentication due to timeout | aditya desai | 11:23 |
Thread | Author | Time |
---|---|---|
Useless memoize path generated for unique join on primary keys | Benjamin Coutu | 11:05 |
Re: Useless memoize path generated for unique join on primary keys | David Rowley | 11:43 |
Re: Useless memoize path generated for unique join on primary keys | Benjamin Coutu | 12:21 |
Re: Useless memoize path generated for unique join on primary keys | David Rowley | 12:31 |
Window partial fetch optimization | Levi Aul | 18:11 |
Re: Window partial fetch optimization | David Rowley | 22:12 |
Thread | Author | Time |
---|---|---|
Re: Window partial fetch optimization | Jeff Janes | 21:56 |
Why is there a Sort after an Index Only Scan? | André Hänsel | 23:15 |
Re: Why is there a Sort after an Index Only Scan? | Jeff Janes | 23:37 |
Re: Why is there a Sort after an Index Only Scan? | David Rowley | 23:42 |
Thread | Author | Time |
---|---|---|
RE: Why is there a Sort after an Index Only Scan? | André Hänsel | 01:12 |
Re: Why is there a Sort after an Index Only Scan? | Tom Lane | 02:08 |
Thread | Author | Time |
---|---|---|
DB connection issue suggestions | Sudhir Guna | 16:59 |
Re: DB connection issue suggestions 📎 | MichaelDBA Vitale | 18:13 |
Re: DB connection issue suggestions | Justin Pryzby | 18:15 |
Re: DB connection issue suggestions | Ranier Vilela | 18:54 |
Thread | Author | Time |
---|---|---|
Re: DB connection issue suggestions | Sudhir Guna | 01:44 |
Re: DB connection issue suggestions | Sudhir Guna | 01:46 |
Re: DB connection issue suggestions | Sudhir Guna | 01:52 |
Re: DB connection issue suggestions | Laurenz Albe | 06:13 |
Re: DB connection issue suggestions | Anbazhagan M | 06:30 |
Re: DB connection issue suggestions | Sudhir Guna | 07:11 |
Re: DB connection issue suggestions | Ranier Vilela | 11:45 |
Re: DB connection issue suggestions | Justin Pryzby | 19:09 |
Thread | Author | Time |
---|---|---|
Re: DB connection issue suggestions | Sudhir Guna | 04:53 |
Thread | Author | Time |
---|---|---|
Re: DB connection issue suggestions | Justin Pryzby | 04:08 |
Thread | Author | Time |
---|---|---|
Need help on Query Tunning and Not using the Index Scan | Kumar, Mukesh | 07:37 |
Selecting RAM and CPU based on max_connections | aditya desai | 08:27 |
Re: Selecting RAM and CPU based on max_connections | Andreas Kretschmer | 10:15 |
Re: Selecting RAM and CPU based on max_connections | Laurenz Albe | 10:31 |