Mailing lists [pgsql-performance]

1 February 2019

• 21:08   Re: dsa_allocate() faliure Justin Pryzby

4 February 2019

• 10:52   Re: dsa_allocate() faliure Jakub Glapa
• 11:22   Re: dsa_allocate() faliure Thomas Munro
• 12:57   Fw: server hardware tuning. suganthi Sekar
• 17:45   Re: Fw: server hardware tuning. Prince Pathria
• 17:56   Sv: Re: Fw: server hardware tuning. Andreas Joseph Krogh
• 19:42   Re: ERROR: found xmin from before relfrozenxid Mariel Cherkassky
• 23:31   RE: dsa_allocate() faliure Arne Roland

5 February 2019

• 00:47   Re: dsa_allocate() faliure Justin Pryzby
• 23:30   Re: How can sort performance be so different Merlin Moncure

6 February 2019

• 11:38   Re: How can sort performance be so different Laurenz Albe
• 13:29   autovacuum big table taking hours and sometimes seconds Mariel Cherkassky
• 14:16   Re: autovacuum big table taking hours and sometimes seconds Laurenz Albe
• 16:05   Re: autovacuum big table taking hours and sometimes seconds David Rowley
• 16:34   Re: autovacuum big table taking hours and sometimes seconds Mariel Cherkassky
• 16:36   Re: autovacuum big table taking hours and sometimes seconds dangal
• 16:41   Re: autovacuum big table taking hours and sometimes seconds Mariel Cherkassky
• 17:11   Re: autovacuum big table taking hours and sometimes seconds MichaelDBA
• 17:12   Re: autovacuum big table taking hours and sometimes seconds Jeff Janes
• 17:42   Re: autovacuum big table taking hours and sometimes seconds Mariel Cherkassky
• 21:49   Re: autovacuum big table taking hours and sometimes seconds Jeff Janes

7 February 2019

• 01:33   Re: autovacuum big table taking hours and sometimes seconds David Rowley
• 13:38   Transaction size and Wal2Json Mai Peng
• 13:45   Re: Transaction size and Wal2Json Peter Eisentraut
• 14:55   Re: autovacuum big table taking hours and sometimes seconds Mariel Cherkassky
• 19:08   Managing High Availability in PostgreSQL – Part I Kristi Anderson
• 19:26   Re: autovacuum big table taking hours and sometimes seconds Jeff Janes

8 February 2019

• 14:13   Partitioning Optimizer Questions and Issues keith anderson
• 16:04   Re: Partitioning Optimizer Questions and Issues Justin Pryzby

9 February 2019

• 19:45    Evandro Abreu
• 20:16   Re: slow to run query 5000 times Justin Pryzby
• 23:23   Re: slow to run query 5000 times Andres Freund

10 February 2019

• 03:23   Re: slow to run query 5000 times Ricardo Martin Gomez
• 21:43   Re: Tumasgiu Rossini

11 February 2019

• 11:05   Re: Partitioning Optimizer Questions and Issues keith anderson

12 February 2019

• 01:29   Performance regressions found using sqlfuzz Jung, Jinho
• 15:00   Re: Performance regressions found using sqlfuzz Christoph Berg
• 18:08   Bloom index cost model seems to be wrong Thomas Kellerer
• 18:41   Re: Bloom index cost model seems to be wrong Tom Lane
• 19:58   Re: Bloom index cost model seems to be wrong Jeff Janes
• 21:03   Re: Performance regressions found using sqlfuzz Jeff Janes
• 22:56   Re: Bloom index cost model seems to be wrong Jeff Janes

13 February 2019

• 00:17   Re: Bloom index cost model seems to be wrong Tom Lane
• 01:38   Re: Bloom index cost model seems to be wrong Jeff Janes
• 11:34   understanding max_wal_size,wal_keep_segments and checkpoints Mariel Cherkassky
• 12:43   Re: understanding max_wal_size,wal_keep_segments and checkpoints Laurenz Albe
• 13:45   Re: understanding max_wal_size,wal_keep_segments and checkpoints Mariel Cherkassky
• 14:23   Re: understanding max_wal_size,wal_keep_segments and checkpoints Laurenz Albe
• 18:43   ERROR: unrecognized parameter "autovacuum_analyze_scale_factor" Mariel Cherkassky
• 19:13   Re: ERROR: unrecognized parameter "autovacuum_analyze_scale_factor" Alvaro Herrera
• 19:41   Re: ERROR: unrecognized parameter "autovacuum_analyze_scale_factor" Mariel Cherkassky
• 19:54   Re: ERROR: unrecognized parameter "autovacuum_analyze_scale_factor" Alvaro Herrera

14 February 2019

• 10:56   Re: ERROR: unrecognized parameter "autovacuum_analyze_scale_factor" Mariel Cherkassky
• 12:38   Re: server hardware tuning. suganthi Sekar
• 13:05   Re: constraint exclusion with ineq condition (Re: server hardwaretuning.) Justin Pryzby
• 13:38   Re: constraint exclusion with ineq condition (Re: server hardwaretuning.) suganthi Sekar
• 13:40   Re: constraint exclusion with ineq condition (Re: server hardwaretuning.) Justin Pryzby
• 13:49   Re: constraint exclusion with ineq condition (Re: server hardwaretuning.) suganthi Sekar
• 15:37   Re: partition pruning Laurenz Albe
• 15:41   Re: partition pruning suganthi Sekar
• 17:05   Re: constraint exclusion with ineq condition (Re: server hardware tuning.) Michael Lewis
• 17:35   Re: constraint exclusion with ineq condition (Re: server hardwaretuning.) suganthi Sekar
• 17:36   Re: partition pruning Justin Pryzby
• 19:09   Re: autovacuum big table taking hours and sometimes seconds Mariel Cherkassky
• 20:27   Re: Performance regressions found using sqlfuzz Jung, Jinho
• 21:37   Re: autovacuum big table taking hours and sometimes seconds Michael Lewis
• 21:50   Re: constraint exclusion with ineq condition (Re: server hardware tuning.) Michael Lewis
• 22:40   Re: autovacuum big table taking hours and sometimes seconds Mariel Cherkassky
• 22:52   Re: autovacuum big table taking hours and sometimes seconds Michael Lewis
• 23:07   Re: autovacuum big table taking hours and sometimes seconds Mariel Cherkassky
• 23:29   Re: Q on SQL Performance tuning Greg Stark

15 February 2019

• 00:03   Re: JIT overhead slowdown Justin Pryzby
• 00:45   Re: autovacuum big table taking hours and sometimes seconds Michael Lewis
• 08:09   Re: constraint exclusion with ineq condition (Re: server hardwaretuning.) suganthi Sekar
• 09:23   Re: autovacuum big table taking hours and sometimes seconds Mariel Cherkassky
• 11:06   Re: autovacuum big table taking hours and sometimes seconds Laurenz Albe
• 16:39   Re: ERROR: unrecognized parameter "autovacuum_analyze_scale_factor" Alvaro Herrera
• 19:20   Re: Performance regressions found using sqlfuzz Andrew Gierth
• 19:44   Re: Performance regressions found using sqlfuzz Andres Freund
• 20:24   Re: constraint exclusion with ineq condition (Re: server hardware tuning.) Benedict Holland
• 21:00   Re: ERROR: unrecognized parameter "autovacuum_analyze_scale_factor" Mariel Cherkassky

17 February 2019

• 01:04   Re: constraint exclusion with ineq condition (Re: server hardwaretuning.) Justin Pryzby
• 01:37   Re: Performance regressions found using sqlfuzz Tom Lane

18 February 2019

• 01:21   Re: dsa_allocate() faliure Justin Pryzby
• 12:11   Re: dsa_allocate() faliure Jakub Glapa
• 18:49   Re: How can sort performance be so different Bob Jolliffe

19 February 2019

• 00:08   Re: Performance regressions found using sqlfuzz Jung, Jinho
• 18:59   index on jsonb col with 2D array inside the json Mariel Cherkassky
• 19:28   Re: index on jsonb col with 2D array inside the json Michael Lewis
• 19:33   Re: index on jsonb col with 2D array inside the json Mariel Cherkassky
• 19:41   Re: index on jsonb col with 2D array inside the json Michael Lewis
• 21:30   Re: index on jsonb col with 2D array inside the json Mariel Cherkassky

20 February 2019

• 03:10   Why isn't an index scan being used? Abi Noda
• 03:51   Re: Why isn't an index scan being used? David Rowley
• 03:59   Re: Why isn't an index scan being used? Abi Noda
• 06:00   Re: Why isn't an index scan being used? Andrew Gierth
• 07:29   Re: Why isn't an index scan being used? Michael Lewis
• 07:37   Re: Why isn't an index scan being used? Justin Pryzby
• 07:58   Re: Why isn't an index scan being used? Abi Noda
• 11:05   Re: Why isn't an index scan being used? Justin Pryzby
• 17:58   Re: Why isn't an index scan being used? Jeff Janes

21 February 2019

• 00:35   Re: How can sort performance be so different Merlin Moncure
• 00:42   Re: How can sort performance be so different Bob Jolliffe
• 01:25   Re: How can sort performance be so different Peter Geoghegan
• 02:32   neither CPU nor IO bound, but throttled performance Gunther
• 03:54   Re: How can sort performance be so different Peter Geoghegan
• 04:32   Re: neither CPU nor IO bound, but throttled performance Justin Pryzby
• 12:08   Re: neither CPU nor IO bound, but throttled performance Magnus Hagander
• 18:59   Re: neither CPU nor IO bound, but throttled performance Gunther Schadow

22 February 2019

• 18:14   Aggregate and many LEFT JOIN kimaidou
• 18:36   Slow query with aggregate and many LEFT JOINS kimaidou
• 18:54   Re: Aggregate and many LEFT JOIN Justin Pryzby
• 19:14   Re: Aggregate and many LEFT JOIN Michael Lewis
• 19:33   Re: Aggregate and many LEFT JOIN kimaidou
• 20:18   Re: Aggregate and many LEFT JOIN Michael Lewis
• 21:05   Re: Aggregate and many LEFT JOIN Tom Lane
• 22:47   RE: Slow query with aggregate and many LEFT JOINS Igor Neyman
• 22:53   RE: Slow query with aggregate and many LEFT JOINS Igor Neyman

24 February 2019

• 00:05   Massive parallel queue table causes index deterioration, but REINDEX fails with deadlocks. Gunther
• 00:13   Re: Massive parallel queue table causes index deterioration, butREINDEX fails with deadlocks. Peter Geoghegan
• 05:55   Re: Massive parallel queue table causes index deterioration, butREINDEX fails with deadlocks. Gunther
• 09:41   Re: Massive parallel queue table causes index deterioration, butREINDEX fails with deadlocks. David Rowley
• 10:03   Re: Massive parallel queue table causes index deterioration, butREINDEX fails with deadlocks. Justin Pryzby
• 10:25   Re: Massive parallel queue table causes index deterioration, butREINDEX fails with deadlocks. Corey Huinker
• 20:45   Re: Massive parallel queue table causes index deterioration, butREINDEX fails with deadlocks. Gunther
• 23:20   Re: Massive parallel queue table causes index deterioration, butREINDEX fails with deadlocks. Justin Pryzby
• 23:41   Re: Massive parallel queue table causes index deterioration, butREINDEX fails with deadlocks. Peter Geoghegan

25 February 2019

• 00:34   Re: Massive parallel queue table causes index deterioration, butREINDEX fails with deadlocks. Corey Huinker
• 01:43   Re: Massive parallel queue table causes index deterioration, butREINDEX fails with deadlocks. Justin Pryzby
• 01:52   Re: Massive parallel queue table causes index deterioration, butREINDEX fails with deadlocks. Corey Huinker
• 02:33   Re: Massive parallel queue table causes index deterioration, but REINDEX fails with deadlocks. Jeff Janes
• 02:39   Re: Massive parallel queue table causes index deterioration, butREINDEX fails with deadlocks. Jeff Janes
• 06:06   Re: Massive parallel queue table causes index deterioration, butREINDEX fails with deadlocks. Gunther Schadow
• 06:06   Re: Massive parallel queue table causes index deterioration, butREINDEX fails with deadlocks. Gunther
• 06:54   Re: Massive parallel queue table causes index deterioration, butREINDEX fails with deadlocks. Justin Pryzby
• 11:54   Re: Aggregate and many LEFT JOIN kimaidou
• 12:44   Re: Aggregate and many LEFT JOIN kimaidou
• 13:36   Idle backends outside a transaction holding onto large amounts ofmemory / swap space? Tobias Gierke
• 13:41   Query slow for new participants Kim
• 13:52   Re: Idle backends outside a transaction holding onto large amounts ofmemory / swap space? Pavel Stehule
• 19:16   Re: Query slow for new participants Justin Pryzby
• 19:30   Re: Massive parallel queue table causes index deterioration, butREINDEX fails with deadlocks. Corey Huinker
• 21:29   Re: Aggregate and many LEFT JOIN Michael Lewis
• 22:23   Re: Query slow for new participants support@mekong.be
• 23:30   Re: Massive parallel queue table causes index deterioration, but REINDEX fails with deadlocks. Jeff Janes

26 February 2019

• 00:03   Re: Massive parallel queue table causes index deterioration, butREINDEX fails with deadlocks. Jeff Janes
• 00:07   Re: Massive parallel queue table causes index deterioration, butREINDEX fails with deadlocks. MichaelDBA
• 02:22   Re: Query slow for new participants support@mekong.be
• 02:59   Re: Query slow for new participants Justin Pryzby
• 03:30   Re: Query slow for new participants MichaelDBA
• 15:54   Re: Aggregate and many LEFT JOIN kimaidou
• 16:51   Re: Aggregate and many LEFT JOIN Justin Pryzby
• 16:52   Re: Aggregate and many LEFT JOIN Jeff Janes
• 22:08   Re: Query slow for new participants Michael Lewis

27 February 2019

• 00:39   Re: Query slow for new participants support@mekong.be
• 10:58   Re: Query slow for new participants Laurenz Albe
• 17:47   What is pg_stat_user_tables Showing NULL for last_autoanalyze &last_autovacuum Fd Habash
• 19:15   Re: What is pg_stat_user_tables Showing NULL for last_autoanalyze &last_autovacuum Justin Pryzby

28 February 2019

• 11:44   Re: What is pg_stat_user_tables Showing NULL for last_autoanalyze &last_autovacuum Laurenz Albe
• 15:21   How to get the content of Bind variables ROS Didier
• 15:36   Re: How to get the content of Bind variables MichaelDBA
• 15:47   RE: How to get the content of Bind variables ROS Didier
• 16:34   RE: What is pg_stat_user_tables Showing NULL for last_autoanalyze&last_autovacuum Fd Habash
• 19:01   Re: How to get the content of Bind variables Laurenz Albe
• 19:12   RE: How to get the content of Bind variables ROS Didier
• 19:19   Re: How to get the content of Bind variables Justin Pryzby
• 19:43   Re: Performance regressions found using sqlfuzz Jung, Jinho