pgsql-performance since 2019-04-19 00:00

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.

Search the Archives

(enter a message-id to go directly to that message)
Advanced Search

Browse Archives

Prev | Next

April 19, 2019

Thread Author Time
Re: [HACKERS] proposal: schema variables 📎 Pavel Stehule 06:32
Re: Pg10 : Client Configuration for Parallelism ? Thomas Kellerer 06:52
Re: Pg10 : Client Configuration for Parallelism ? Tom Lane 13:43
Re: Out of Memory errors are frustrating as heck! Gaetano Mendola 20:28
Re: Out of Memory errors are frustrating as heck! Justin Pryzby 21:01

April 20, 2019

Thread Author Time
Re: Out of Memory errors are frustrating as heck! Gunther 03:34
Re: Out of Memory errors are frustrating as heck! Jeremy Schneider 05:54
Re: Out of Memory errors are frustrating as heck! Justin Pryzby 07:52
Re: Out of Memory errors are frustrating as heck! Justin Pryzby 10:53
Backup and Restore (pg_dump & pg_restore) Daulat Ram 18:50
Re: Out of Memory errors are frustrating as heck! 📎 Justin Pryzby 19:30
Re: Out of Memory errors are frustrating as heck! Gunther 20:00
Re: Out of Memory errors are frustrating as heck! 📎 Tomas Vondra 20:01
Re: Out of Memory errors are frustrating as heck! Tomas Vondra 20:11
Re: Out of Memory errors are frustrating as heck! Tom Lane 20:26
Re: Out of Memory errors are frustrating as heck! Tomas Vondra 20:36
Re: Out of Memory errors are frustrating as heck! Tom Lane 20:46
Re: Out of Memory errors are frustrating as heck! Tom Lane 20:47
Re: Out of Memory errors are frustrating as heck! Tomas Vondra 20:53
Re: Out of Memory errors are frustrating as heck! 📎 Tomas Vondra 21:13
Re: Out of Memory errors are frustrating as heck! Justin Pryzby 21:45
Re: Out of Memory errors are frustrating as heck! Tom Lane 22:20
Re: Out of Memory errors are frustrating as heck! Tomas Vondra 23:46

April 21, 2019

Thread Author Time
Re: Out of Memory errors are frustrating as heck! Gunther 00:33
Re: Out of Memory errors are frustrating as heck! Tomas Vondra 01:14
Re: Out of Memory errors are frustrating as heck! Gunther 05:03
Re: Out of Memory errors are frustrating as heck! Gunther 05:31
Re: Out of Memory errors are frustrating as heck! 📎 Justin Pryzby 08:08
Re: Out of Memory errors are frustrating as heck! Justin Pryzby 10:19
Re: Out of Memory errors are frustrating as heck! 📎 Tomas Vondra 11:46
Re: Out of Memory errors are frustrating as heck! Jeff Janes 13:05
Re: Out of Memory errors are frustrating as heck! Tom Lane 14:36
Re: Out of Memory errors are frustrating as heck! Tomas Vondra 16:15
Re: Backup and Restore (pg_dump & pg_restore) Tomas Vondra 16:18
Backup and Restore (pg_dump & pg_restore) Daulat Ram 16:35
Re: Out of Memory errors are frustrating as heck! 📎 Justin Pryzby 16:40
Re: Backup and Restore (pg_dump & pg_restore) Adrian Klaver 18:46
Re: Backup and Restore (pg_dump & pg_restore) Tom Lane 19:25
Re: Backup and Restore (pg_dump & pg_restore) Ron 20:42
Re: Backup and Restore (pg_dump & pg_restore) Adrian Klaver 20:58
Re: Backup and Restore (pg_dump & pg_restore) Ron 21:20
Re: Backup and Restore (pg_dump & pg_restore) Adrian Klaver 22:13
Re: Out of Memory errors are frustrating as heck! Tom Lane 23:07
Re: Out of Memory errors are frustrating as heck! Gunther 23:25
Re: Out of Memory errors are frustrating as heck! Tomas Vondra 23:51
Re: Out of Memory errors are frustrating as heck! Gunther 23:58

April 22, 2019

Thread Author Time
Re: Out of Memory errors are frustrating as heck! Gunther 00:55
Re: Out of Memory errors are frustrating as heck! 📎 Tomas Vondra 03:09
Re: Out of Memory errors are frustrating as heck! Gaetano Mendola 08:07
Re: Out of Memory errors are frustrating as heck! Tomas Vondra 13:04
Re: Out of Memory errors are frustrating as heck! Jeff Janes 17:15
Re: Out of Memory errors are frustrating as heck! Tom Lane 17:57

April 23, 2019

Thread Author Time
Re: Out of Memory errors are frustrating as heck! Gunther 20:37
Re: Out of Memory errors are frustrating as heck! Justin Pryzby 20:43
Re: Out of Memory errors are frustrating as heck! Tomas Vondra 21:46
Re: Out of Memory errors are frustrating as heck! Tomas Vondra 21:59
Re: Out of Memory errors are frustrating as heck! Gunther 23:09

April 24, 2019

Thread Author Time
Re: Out of Memory errors are frustrating as heck! Tomas Vondra 00:36

April 28, 2019

Thread Author Time
Re: Out of Memory errors are frustrating as heck! 📎 Tomas Vondra 14:19

April 29, 2019

Thread Author Time
Generic Plans for Prepared Statement are 158155 times slower than Custom Plans Naik, Sameer 10:36
Re: Generic Plans for Prepared Statement are 158155 times slower than Custom Plans Bruce Momjian 13:36
Re: Generic Plans for Prepared Statement are 158155 times slower than Custom Plans Tom Lane 14:35
Re: Generic Plans for Prepared Statement are 158155 times slower than Custom Plans Andres Freund 16:23
Re: Generic Plans for Prepared Statement are 158155 times slower than Custom Plans Tom Lane 16:51

April 30, 2019

Thread Author Time
RE: Re: Generic Plans for Prepared Statement are 158155 times slower than Custom Plans Naik, Sameer 04:58
Failure to reordering in case of a lateral join in combination with a left join (not inner join) resulting in suboptimal nested loop plan Peter Billen 18:57
Re: Failure to reordering in case of a lateral join in combination with a left join (not inner join) resulting in suboptimal nested loop plan Tom Lane 20:38

May 6, 2019

Thread Author Time
PostgreSQL optimizer use seq scan instead of pkey index only scan (in queries with postgres_fdw) Vitaly Baranovsky 14:43
Re: PostgreSQL optimizer use seq scan instead of pkey index only scan (in queries with postgres_fdw) Jeff Janes 15:32
Re: PostgreSQL optimizer use seq scan instead of pkey index only scan (in queries with postgres_fdw) Vitaly Baranovsky 15:38
Re: PostgreSQL optimizer use seq scan instead of pkey index only scan (in queries with postgres_fdw) Tom Lane 15:53
Re: PostgreSQL optimizer use seq scan instead of pkey index only scan (in queries with postgres_fdw) Jeff Janes 15:53
Re: PostgreSQL optimizer use seq scan instead of pkey index only scan (in queries with postgres_fdw) Vitaly Baranovsky 16:36
Re: PostgreSQL optimizer use seq scan instead of pkey index only scan (in queries with postgres_fdw) Jeff Janes 17:17

May 7, 2019

Thread Author Time
GCC 8.3.0 vs. 9.0.1 Steven Winfield 16:14
Re: GCC 8.3.0 vs. 9.0.1 Tom Lane 17:05
Re: GCC 8.3.0 vs. 9.0.1 Peter Geoghegan 17:28
Re: GCC 8.3.0 vs. 9.0.1 Andres Freund 17:32
Re: GCC 8.3.0 vs. 9.0.1 Andres Freund 17:42
Re: GCC 8.3.0 vs. 9.0.1 Andres Freund 18:04

May 9, 2019

Thread Author Time
Re: Re: Generic Plans for Prepared Statement are 158155 times slower than Custom Plans Deepak Somaiya 04:14
Re: [HACKERS] proposal: schema variables 📎 Pavel Stehule 04:34
integrate Postgres Users Authentication with our own LDAP Server M Tarkeshwar Rao 04:51
Re: integrate Postgres Users Authentication with our own LDAP Server Achilleas Mantzios 06:17
Re: integrate Postgres Users Authentication with our own LDAP Server Laurenz Albe 06:42
RE: integrate Postgres Users Authentication with our own LDAP Server M Tarkeshwar Rao 07:11
Re: integrate Postgres Users Authentication with our own LDAP Server Laurenz Albe 07:23
Re: integrate Postgres Users Authentication with our own LDAP Server Tomas Vondra 12:43
RE: GCC 8.3.0 vs. 9.0.1 Steven Winfield 14:04
Re: integrate Postgres Users Authentication with our own LDAP Server Stephen Frost 19:24

May 10, 2019

Thread Author Time
Log size in bytes of query result Franklin Haut 14:10
Re: Log size in bytes of query result Laurenz Albe 16:09
Re: Log size in bytes of query result Sergei Kornilov 16:42

May 12, 2019

Thread Author Time
Huge generated UNION ALL faster than JOIN? Ancoron Luciferis 14:08
Re: Huge generated UNION ALL faster than JOIN? Tom Lane 18:08
Re: Huge generated UNION ALL faster than JOIN? Ancoron Luciferis 22:23

May 14, 2019

Thread Author Time
The wrong (?) query plan for queries with remote (postgres_fdw) tables 📎 Vitaly Baranovsky 16:08

May 16, 2019

Thread Author Time
Analyze results in more expensive query plan Jeremy Altavilla 20:03

May 17, 2019

Thread Author Time
RE: Re: Re: Generic Plans for Prepared Statement are 158155 times slower than Custom Plans Naik, Sameer 06:42
using sequential scan instead of index for join with a union Kent Tong 09:15
Re: using sequential scan instead of index for join with a union Sergei Kornilov 09:23
Re: using sequential scan instead of index for join with a union Kent Tong 09:36
Re: Analyze results in more expensive query plan Tom Lane 13:35

May 20, 2019

Thread Author Time
Trying to handle db corruption 9.6 Mariel Cherkassky 14:39
Re: Trying to handle db corruption 9.6 Flo Rance 14:49
Re: Trying to handle db corruption 9.6 Mariel Cherkassky 15:00
Re: Trying to handle db corruption 9.6 Mariel Cherkassky 16:07
Re: Trying to handle db corruption 9.6 Bimal 16:20
Re: Trying to handle db corruption 9.6 Mariel Cherkassky 17:20
Re: Analyze results in more expensive query plan Jeremy Altavilla 20:19
Re: Trying to handle db corruption 9.6 Tomas Vondra 20:55
Re: Trying to handle db corruption 9.6 Tomas Vondra 21:04
Re: Re: Re: Generic Plans for Prepared Statement are 158155 times slower than Custom Plans Deepak Somaiya 21:37
Re: Generic Plans for Prepared Statement are 158155 times slower than Custom Plans Tomas Vondra 22:16

May 21, 2019

Thread Author Time
Temporarily very slow planning time after a big delete Walter Smith 00:43
Re: Temporarily very slow planning time after a big delete David Rowley 01:00
Re: Temporarily very slow planning time after a big delete Tom Lane 01:04
Re: Analyze results in more expensive query plan David Rowley 02:04
Re: Temporarily very slow planning time after a big delete Walter Smith 02:04
Re: Temporarily very slow planning time after a big delete Walter Smith 02:12
Re: Temporarily very slow planning time after a big delete David Rowley 02:15
Re: Trying to handle db corruption 9.6 Mariel Cherkassky 09:01
Re: Trying to handle db corruption 9.6 Tomas Vondra 13:07
Re: Trying to handle db corruption 9.6 Mariel Cherkassky 13:12
Re: Trying to handle db corruption 9.6 Tomas Vondra 16:37
Re: Temporarily very slow planning time after a big delete Walter Smith 18:12
Re: Temporarily very slow planning time after a big delete Peter Geoghegan 18:15
Re: Temporarily very slow planning time after a big delete Walter Smith 18:16
Re: Temporarily very slow planning time after a big delete Peter Geoghegan 18:17
Re: Temporarily very slow planning time after a big delete Walter Smith 18:26
Re: Temporarily very slow planning time after a big delete didier 18:32
Re: Temporarily very slow planning time after a big delete Peter Geoghegan 18:36

May 22, 2019

Thread Author Time
Use Postgres as a column store by creating one table per column Lev Kokotov 04:28
Re: Use Postgres as a column store by creating one table per column Justin Pryzby 04:43
Re: Log size in bytes of query result Franklin Haut 12:50
Re: Log size in bytes of query result Dmitry Dolgov 13:15
pg_restore takes more time on creation of rules Mariel Cherkassky 15:26
Re: pg_restore takes more time on creation of rules Tomas Vondra 15:41
Re: pg_restore takes more time on creation of rules Mariel Cherkassky 15:44
Re: pg_restore takes more time on creation of rules Ron 16:00
Re: pg_restore takes more time on creation of rules Mariel Cherkassky 16:02
Re: pg_restore takes more time on creation of rules Ron 16:27
Re: pg_restore takes more time on creation of rules Mariel Cherkassky 16:44
Re: pg_restore takes more time on creation of rules Tomas Vondra 17:00
Re: Analyze results in more expensive query plan Jeremy Altavilla 22:21

May 23, 2019

Thread Author Time
Re: Use Postgres as a column store by creating one table per column George Neuner 05:08
RE: Re: Generic Plans for Prepared Statement are 158155 times slower than Custom Plans Naik, Sameer 06:37
upgrade to PG11 on secondary fails (no initdb was launched) Mariel Cherkassky 08:20
Fwd: upgrade to PG11 on secondary fails (no initdb was launched) Mariel Cherkassky 08:58
Fwd: upgrade to PG11 on secondary fails (no initdb was launched) Mariel Cherkassky 11:07
RE: upgrade to PG11 on secondary fails (no initdb was launched) Greg Clough 11:23
Re: Fwd: upgrade to PG11 on secondary fails (no initdb was launched) Fabio Pardi 11:31
Re: Fwd: upgrade to PG11 on secondary fails (no initdb was launched) Stephen Frost 15:06
Re: upgrade to PG11 on secondary fails (no initdb was launched) Stephen Frost 15:08
Re: Generic Plans for Prepared Statement are 158155 times slower than Custom Plans Tom Lane 17:17

May 24, 2019

Thread Author Time
Re: [HACKERS] proposal: schema variables 📎 Pavel Stehule 17:12
Re: Use Postgres as a column store by creating one table per column Tomas Vondra 18:06
Re: Use Postgres as a column store by creating one table per column Stephen Frost 19:38

May 25, 2019

Thread Author Time
Re: Use Postgres as a column store by creating one table per column Mark Kirkwood 03:55
UUID v1 optimizations... Ancoron Luciferis 13:45
Re: UUID v1 optimizations... Peter Eisentraut 14:19
Re: UUID v1 optimizations... Tom Lane 14:57
Re: UUID v1 optimizations... Ancoron Luciferis 17:27
Re: UUID v1 optimizations... Ancoron Luciferis 18:20
Re: UUID v1 optimizations... Vitalii Tymchyshyn 19:00
Re: UUID v1 optimizations... Ancoron Luciferis 21:02
Re: UUID v1 optimizations... Ancoron Luciferis 21:02
Re: UUID v1 optimizations... Tom Lane 21:54
Re: UUID v1 optimizations... Tomas Vondra 22:14
Re: UUID v1 optimizations... Tom Lane 22:38
Re: UUID v1 optimizations... Ancoron Luciferis 23:00
Re: UUID v1 optimizations... Tomas Vondra 23:44
Re: UUID v1 optimizations... Ancoron Luciferis 23:49

May 26, 2019

Thread Author Time
Re: UUID v1 optimizations... Tomas Vondra 01:09
Re: UUID v1 optimizations... Morris de Oryx 04:27
Re: UUID v1 optimizations... Ancoron Luciferis 09:01
Re: UUID v1 optimizations... Ancoron Luciferis 09:38
Re: UUID v1 optimizations... Morris de Oryx 10:24
Re: UUID v1 optimizations... Tomas Vondra 10:37
Re: UUID v1 optimizations... Morris de Oryx 10:38
Re: UUID v1 optimizations... Morris de Oryx 10:46

May 27, 2019

Thread Author Time
improve wals replay on secondary Mariel Cherkassky 08:49
Re: improve wals replay on secondary Fabio Pardi 09:12
Re: improve wals replay on secondary Fabio Pardi 09:29
Re: improve wals replay on secondary Mariel Cherkassky 10:17
Re: improve wals replay on secondary Fabio Pardi 11:04

May 28, 2019

Thread Author Time
Re: improve wals replay on secondary Fabio Pardi 10:54

May 29, 2019

Thread Author Time
Re: improve wals replay on secondary Mariel Cherkassky 07:20
JIT in PostgreSQL 12 ? Tobias Gierke 08:02
Re: improve wals replay on secondary Fabio Pardi 08:20
Re: improve wals replay on secondary Mariel Cherkassky 08:39
Sv: JIT in PostgreSQL 12 ? Andreas Joseph Krogh 08:48
Re: Sv: JIT in PostgreSQL 12 ? Tobias Gierke 09:13
Re: Sv: JIT in PostgreSQL 12 ? Andreas Joseph Krogh 09:16
Re: JIT in PostgreSQL 12 ? Andreas Karlsson 09:37
Re: improve wals replay on secondary Nikolay Samokhvalov 10:54
Re: improve wals replay on secondary Mariel Cherkassky 11:10

May 30, 2019

Thread Author Time
Shortest offline window on database migration Haroldo Kerry 15:08
Re: Shortest offline window on database migration Tomas Vondra 15:31
RE: Shortest offline window on database migration Steven Winfield 15:54

Browse Archives

Prev | Next