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: proposal: schema variables 📎 | Pavel Stehule | 17:30 |
Thread | Author | Time |
---|---|---|
High kswapd | Don Seiler | 14:34 |
Re: High kswapd | Justin Pryzby | 14:42 |
Re: High kswapd | Don Seiler | 14:46 |
Re: High kswapd | Justin Pryzby | 14:58 |
Re: PostgreSQL DBA consulting | Amol Tarte | 15:04 |
Re: High kswapd | Don Seiler | 15:08 |
Thread | Author | Time |
---|---|---|
Duplicate WHERE condition changes performance and plan | singh400@gmail.com | 19:55 |
Using unlogged tables for web sessions | Stephen Carboni | 22:53 |
Re: Duplicate WHERE condition changes performance and plan | David Rowley | 23:57 |
Thread | Author | Time |
---|---|---|
RE: Postgres not using index on views | Rick Vincent | 14:28 |
Postgres not using index on views | David G. Johnston | 14:55 |
RE: Postgres not using index on views | Rick Vincent | 15:12 |
Thread | Author | Time |
---|---|---|
Re: Duplicate WHERE condition changes performance and plan | singh400@gmail.com | 00:50 |
Re: Duplicate WHERE condition changes performance and plan | Justin Pryzby | 02:33 |
RE: Postgres not using index on views | Rick Vincent | 11:10 |
Thread | Author | Time |
---|---|---|
Re: Duplicate WHERE condition changes performance and plan | singh400@gmail.com | 16:33 |
Re: PostgreSQL does not choose my indexes well | Jeff Janes | 18:26 |
Re: PostgreSQL does not choose my indexes well | Stephen Frost | 18:33 |
Re: PostgreSQL does not choose my indexes well | Tom Lane | 19:39 |
The query plan get all columns but I'm using only one column. | Moises Lopez | 21:11 |
Re: PostgreSQL does not choose my indexes well | Jeff Janes | 22:59 |
Thread | Author | Time |
---|---|---|
Re: PostgreSQL does not choose my indexes well | Stephen Frost | 12:02 |
Re: The query plan get all columns but I'm using only one column. | Tom Lane | 14:24 |
Re: PostgreSQL does not choose my indexes well | Arcadio Ortega Reinoso | 19:47 |
Re: The query plan get all columns but I'm using only one column. | Michael Lewis | 20:40 |
Thread | Author | Time |
---|---|---|
Recursive query slow on strange conditions | Jean-Christophe Boggio | 17:49 |
Re: Recursive query slow on strange conditions | Justin Pryzby | 18:10 |
Re: Recursive query slow on strange conditions | Andreas Joseph Krogh | 19:37 |
Re: Recursive query slow on strange conditions | Jean-Christophe Boggio | 20:22 |
Thread | Author | Time |
---|---|---|
NUMA settings | Marc Rechté | 06:54 |
Re: NUMA settings | Laurenz Albe | 08:50 |
Re: The query plan get all columns but I'm using only one column. 📎 | Moises Lopez | 19:21 |
Re: The query plan get all columns but I'm using only one column. | Michael Lewis | 19:36 |
Thread | Author | Time |
---|---|---|
Re: The query plan get all columns but I'm using only one column. | Michael Lewis | 15:52 |
Re: The query plan get all columns but I'm using only one column. | Moises Lopez | 16:26 |
Thread | Author | Time |
---|---|---|
Best partition type for billions of addresses | Arya F | 13:20 |
Re: Best partition type for billions of addresses | Justin Pryzby | 14:00 |
Re: Best partition type for billions of addresses | Stephen Frost | 14:01 |
Re: Best partition type for billions of addresses | Arya F | 14:33 |
Re: Best partition type for billions of addresses | Stephen Frost | 14:39 |
Thread | Author | Time |
---|---|---|
Please help! Query jumps from 1s -> 4m | James Thompson | 08:58 |
Re: Duplicate WHERE condition changes performance and plan | singh400@gmail.com | 11:39 |
Re: Please help! Query jumps from 1s -> 4m | Justin Pryzby | 15:38 |
Thread | Author | Time |
---|---|---|
Re: good book or any other resources for Postgresql | Bhupendra Babu | 03:37 |
Re: NUMA settings | Marc Rechté | 05:56 |
Re: NUMA settings | Laurenz Albe | 08:00 |
Re: Please help! Query jumps from 1s -> 4m | Laurenz Albe | 08:08 |
Re: NUMA settings | Marc Rechté | 08:11 |
Re: NUMA settings | Laurenz Albe | 08:25 |
Re: Please help! Query jumps from 1s -> 4m | Justin Pryzby | 19:28 |
Re: Please help! Query jumps from 1s -> 4m | James Thompson | 21:10 |
Re: Please help! Query jumps from 1s -> 4m | Justin Pryzby | 21:35 |
Re: Please help! Query jumps from 1s -> 4m | Tom Lane | 21:42 |
Thread | Author | Time |
---|---|---|
Re: 600 million rows of data. Bad hardware or need partitioning? | Arya F | 00:15 |
Re: 600 million rows of data. Bad hardware or need partitioning? | Arya F | 00:31 |
Re: 600 million rows of data. Bad hardware or need partitioning? | Justin Pryzby | 01:37 |
Inaccurate Rows estimate for "Bitmap And" causes Planner to choose wrong join | Steve Pritchard | 16:19 |
Re: Inaccurate Rows estimate for "Bitmap And" causes Planner to choose wrong join | Justin Pryzby | 16:34 |
Re: Inaccurate Rows estimate for "Bitmap And" causes Planner to choose wrong join | Jeff Janes | 18:24 |
Thread | Author | Time |
---|---|---|
Re: 600 million rows of data. Bad hardware or need partitioning? | Arya F | 04:10 |
Thread | Author | Time |
---|---|---|
Re: AutoVacuum and growing transaction XID's | github kran | 15:40 |
Thread | Author | Time |
---|---|---|
Re: Inaccurate Rows estimate for "Bitmap And" causes Planner to choose wrong join | Steve Pritchard | 09:33 |
Re: Please help! Query jumps from 1s -> 4m | James Thompson | 14:17 |
Thread | Author | Time |
---|---|---|
Plan not skipping unnecessary inner join | Matthew Nelson | 05:44 |
Re: Plan not skipping unnecessary inner join | David Wheeler | 06:45 |
Thread | Author | Time |
---|---|---|
Re: Plan not skipping unnecessary inner join | Matthew Nelson | 17:36 |
Thread | Author | Time |
---|---|---|
Re: Plan not skipping unnecessary inner join | Ranier Vilela | 12:32 |
Re: Plan not skipping unnecessary inner join | Justin Pryzby | 13:31 |
Re: Plan not skipping unnecessary inner join | Ranier Vilela | 14:05 |
Thread | Author | Time |
---|---|---|
Execution time from >1s -> 80m+ when extra columns added in SELECT for sub-query 📎 | A Guy Named Ryan | 18:42 |
Re: Execution time from >1s -> 80m+ when extra columns added in SELECT for sub-query | Pavel Stehule | 19:17 |
Re: Execution time from >1s -> 80m+ when extra columns added in SELECT for sub-query | A Guy Named Ryan | 20:49 |
Re: Execution time from >1s -> 80m+ when extra columns added in SELECT for sub-query | Tom Lane | 21:58 |
Thread | Author | Time |
---|---|---|
OOM Killer kills PostgreSQL | Piotr Włodarczyk | 07:30 |
Re: OOM Killer kills PostgreSQL | Laurenz Albe | 08:22 |
Re: OOM Killer kills PostgreSQL | Piotr Włodarczyk | 08:28 |
Re: OOM Killer kills PostgreSQL | Fabio Pardi | 08:40 |
Re: OOM Killer kills PostgreSQL | Justin Pryzby | 08:46 |
Re: OOM Killer kills PostgreSQL | Stephen Frost | 16:54 |
Suggestion to improve query performance. | postgann2020 s | 18:20 |
Thread | Author | Time |
---|---|---|
Re: proposal: schema variables | Pavel Stehule | 10:10 |
Re: proposal: schema variables | Amit Kapila | 11:34 |
Re: proposal: schema variables 📎 | Pavel Stehule | 12:49 |
Suggestion on table analyze | postgann2020 s | 14:18 |
Suggestion on index creation for TEXT data field | postgann2020 s | 14:27 |
Re: Suggestion on index creation for TEXT data field | David G. Johnston | 14:36 |
Re: Suggestion on table analyze | Adrian Klaver | 14:41 |
Re: Suggestion on index creation for TEXT data field | postgann2020 s | 14:44 |
Re: Suggestion on index creation for TEXT data field | Adrian Klaver | 14:45 |
Re: Suggestion on table analyze | postgann2020 s | 14:48 |
Re: Suggestion on index creation for TEXT data field | David G. Johnston | 14:51 |
Re: Suggestion on index creation for TEXT data field | postgann2020 s | 14:53 |
Thread | Author | Time |
---|---|---|
Date vs Timestamp without timezone Partition Key | Cedric Leong | 03:50 |
Re: Date vs Timestamp without timezone Partition Key | Tom Lane | 04:48 |
Re: Request to help on Query improvement suggestion. | Laurenz Albe | 06:47 |
Thread | Author | Time |
---|---|---|
PostgreSQL performance problem moving from 9.6.17 to 12.3 | Kenneth Marshall | 15:56 |
Re: PostgreSQL performance problem moving from 9.6.17 to 12.3 | Tom Lane | 16:42 |
Thread | Author | Time |
---|---|---|
Performance tunning | sugnathi hai | 07:36 |
Re: Performance tunning | Pavel Stehule | 07:43 |
Re: Performance tunning | Justin Pryzby | 14:19 |
Re: Performance tunning | Jeff Janes | 14:55 |
Thread | Author | Time |
---|---|---|
Configuration | sugnathi hai | 12:09 |
Re: Configuration | Filip Rembiałkowski | 13:24 |
Thread | Author | Time |
---|---|---|
When to use PARTITION BY HASH? | Oleksandr Shulgin | 17:17 |
Re: When to use PARTITION BY HASH? | Justin Pryzby | 17:33 |
Re: When to use PARTITION BY HASH? | MichaelDBA | 17:39 |
Re: When to use PARTITION BY HASH? | David G. Johnston | 17:43 |
Re: When to use PARTITION BY HASH? | Michel Pelletier | 17:45 |
Re: When to use PARTITION BY HASH? | Stephen Frost | 17:47 |
Thread | Author | Time |
---|---|---|
Re: When to use PARTITION BY HASH? | Oleksandr Shulgin | 07:38 |
Re: When to use PARTITION BY HASH? | Oleksandr Shulgin | 07:45 |
Re: When to use PARTITION BY HASH? | Oleksandr Shulgin | 11:55 |
Re: When to use PARTITION BY HASH? | Justin Pryzby | 15:09 |
increased max_parallel_workers_per_gather results in fewer workers? | Philip Semanchuk | 20:04 |
Re: increased max_parallel_workers_per_gather results in fewer workers? | Justin Pryzby | 21:15 |
Re: increased max_parallel_workers_per_gather results in fewer workers? | Philip Semanchuk | 22:23 |
Re: increased max_parallel_workers_per_gather results in fewer workers? | Justin Pryzby | 22:36 |
Thread | Author | Time |
---|---|---|
Re: increased max_parallel_workers_per_gather results in fewer workers? | Sebastian Dressler | 06:28 |
Re: increased max_parallel_workers_per_gather results in fewer workers? | Luis Carril | 06:41 |
Re: increased max_parallel_workers_per_gather results in fewer workers? | Tomas Vondra | 08:56 |
Re: increased max_parallel_workers_per_gather results in fewer workers? | Magnus Hagander | 09:30 |