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 |
|---|---|---|
| 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 |
| Re: When to use PARTITION BY HASH? | Jeff Janes | 14:32 |
| Re: increased max_parallel_workers_per_gather results in fewer workers? | Philip Semanchuk | 16:41 |
| Re: increased max_parallel_workers_per_gather results in fewer workers? | Sebastian Dressler | 17:45 |
| Re: increased max_parallel_workers_per_gather results in fewer workers? | Philip Semanchuk | 18:37 |
| Re: increased max_parallel_workers_per_gather results in fewer workers? | Sebastian Dressler | 19:03 |
| Re: increased max_parallel_workers_per_gather results in fewer workers? | Philip Semanchuk | 21:29 |
| Thread | Author | Time |
|---|---|---|
| Postgresql server gets stuck at low load | Krzysztof Olszewski | 10:07 |
| Re: When to use PARTITION BY HASH? | Oleksandr Shulgin | 10:11 |
| Re: Postgresql server gets stuck at low load | luis.roberto | 11:16 |
| Re: Postgresql server gets stuck at low load | Pavel Stehule | 11:37 |
| Re: When to use PARTITION BY HASH? | Imre Samu | 11:48 |
| Re: When to use PARTITION BY HASH? | Jeff Janes | 13:51 |
| Thread | Author | Time |
|---|---|---|
| Re: Date vs Timestamp without timezone Partition Key | Cedric Leong | 02:12 |
| Re: Date vs Timestamp without timezone Partition Key | David Rowley | 02:16 |
| Re: Date vs Timestamp without timezone Partition Key | Cedric Leong | 02:49 |
| Re: Date vs Timestamp without timezone Partition Key | David Rowley | 03:13 |
| Re: Date vs Timestamp without timezone Partition Key | Cedric Leong | 03:56 |
| Re: When to use PARTITION BY HASH? | Michel Pelletier | 16:13 |
| Thread | Author | Time |
|---|---|---|
| Re: When to use PARTITION BY HASH? | Ron | 01:58 |
| Re: When to use PARTITION BY HASH? | MichaelDBA | 11:41 |
| Re: When to use PARTITION BY HASH? | David Rowley | 21:23 |
| Thread | Author | Time |
|---|---|---|
| Re: When to use PARTITION BY HASH? | Oleksandr Shulgin | 08:40 |
| Re: When to use PARTITION BY HASH? | [email protected] | 09:50 |
| Re: When to use PARTITION BY HASH? | Ron | 13:07 |
| Re: When to use PARTITION BY HASH? | David Rowley | 21:25 |
| Thread | Author | Time |
|---|---|---|
| Re: Postgresql server gets stuck at low load | Krzysztof Olszewski | 11:52 |
| Re: Postgresql server gets stuck at low load | Krzysztof Olszewski | 11:54 |
| Re: Postgresql server gets stuck at low load | Avinash Kumar | 12:01 |
| Re: Postgresql server gets stuck at low load | Krzysztof Olszewski | 12:05 |
| Re: Postgresql server gets stuck at low load | Justin Pryzby | 12:09 |
| Thread | Author | Time |
|---|---|---|
| Windows slowness? | Mikkel Lauritsen | 19:28 |
| Re: Windows slowness? | mountain the blue | 20:35 |
| Re: Windows slowness? | David Rowley | 21:08 |
| Thread | Author | Time |
|---|---|---|
| Re: Windows slowness? | Mikkel Lauritsen | 05:05 |
| Thread | Author | Time |
|---|---|---|
| view reading information_schema is slow in PostgreSQL 12 | regrog | 15:21 |
| Re: view reading information_schema is slow in PostgreSQL 12 | Imre Samu | 19:00 |
| Thread | Author | Time |
|---|---|---|
| Re: view reading information_schema is slow in PostgreSQL 12 | Tom Lane | 03:11 |
| Re: view reading information_schema is slow in PostgreSQL 12 | David Rowley | 03:15 |
| Re: view reading information_schema is slow in PostgreSQL 12 | David Rowley | 03:55 |
| Re: view reading information_schema is slow in PostgreSQL 12 | Tom Lane | 04:07 |
| Re: view reading information_schema is slow in PostgreSQL 12 | Justin Pryzby | 04:34 |
| Re: view reading information_schema is slow in PostgreSQL 12 | Pavel Stehule | 05:13 |
| Re: view reading information_schema is slow in PostgreSQL 12 | Pavel Stehule | 05:15 |
| Re: view reading information_schema is slow in PostgreSQL 12 | Pavel Stehule | 05:23 |
| Re: view reading information_schema is slow in PostgreSQL 12 | David Rowley | 07:52 |
| Re: view reading information_schema is slow in PostgreSQL 12 | David Rowley | 08:22 |
| Re: view reading information_schema is slow in PostgreSQL 12 | Tom Lane | 17:06 |
| Thread | Author | Time |
|---|---|---|
| Performance issue | Nagaraj Raj | 22:45 |
| Re: Performance issue | David Rowley | 23:55 |
| Thread | Author | Time |
|---|---|---|
| Re: Performance issue | Justin Pryzby | 00:05 |
| Re: view reading information_schema is slow in PostgreSQL 12 | Michael Lewis | 18:21 |
| Thread | Author | Time |
|---|---|---|
| Re: view reading information_schema is slow in PostgreSQL 12 | regrog | 09:23 |
| simple query running for ever | Nagaraj Raj | 20:35 |
| Re: simple query running for ever | Michael Lewis | 20:43 |
| Re: simple query running for ever | Justin Pryzby | 20:46 |
| Re: simple query running for ever | Nagaraj Raj | 20:57 |
| Re: simple query running for ever | Nagaraj Raj | 21:13 |
| Re: simple query running for ever | Nagaraj Raj | 21:15 |
| Re: simple query running for ever | Justin Pryzby | 22:05 |
| Re: simple query running for ever | Andreas Joseph Krogh | 22:10 |
| Re: simple query running for ever | Justin Pryzby | 22:33 |
| Thread | Author | Time |
|---|---|---|
| Re: simple query running for ever | Laurenz Albe | 09:23 |
| Thread | Author | Time |
|---|---|---|
| Re: PostgreSQL 12.3 slow index scan chosen | Tom Lane | 18:22 |
| Re: PostgreSQL 12.3 slow index scan chosen | Kenneth Marshall | 19:55 |
| Thread | Author | Time |
|---|---|---|
| Re: PostgreSQL 12.3 slow index scan chosen | Alvaro Herrera | 19:27 |
| Re: PostgreSQL 12.3 slow index scan chosen | Kenneth Marshall | 19:29 |
| Re: PostgreSQL 12.3 slow index scan chosen | Tom Lane | 19:39 |
| Thread | Author | Time |
|---|---|---|
| Recommended value for pg_test_fsync | Nikhil Shetty | 09:26 |
| Re: Recommended value for pg_test_fsync | Bruce Momjian | 16:06 |
| Thread | Author | Time |
|---|---|---|
| Re: Recommended value for pg_test_fsync | Nikhil Shetty | 05:02 |
| Re: Recommended value for pg_test_fsync | Bruce Momjian | 15:24 |
| Is there a known bug with SKIP LOCKED and "tuple to be locked was already moved to another partition due to concurrent update"? | Gunther Schadow | 16:10 |
| Re: Recommended value for pg_test_fsync | Jeff Janes | 16:21 |
| Re: Recommended value for pg_test_fsync | Jeff Janes | 17:26 |