pg.ddx.io pgsql-performance@postgresql.org mailing list archive
help / color / mirror / Atom feedAggregate and many LEFT JOIN
2019-02-22 15:14 UTC kimaidou <kimaidou@gmail.com>
` Re: Aggregate and many LEFT JOIN
2019-02-22 15:54 UTC Justin Pryzby <pryzby@telsasoft.com>
` Re: Aggregate and many LEFT JOIN
2019-02-22 16:14 UTC Michael Lewis <mlewis@entrata.com>
` Re: Aggregate and many LEFT JOIN
2019-02-22 16:33 UTC kimaidou <kimaidou@gmail.com>
` Re: Aggregate and many LEFT JOIN
2019-02-22 17:18 UTC Michael Lewis <mlewis@entrata.com>
` Re: Aggregate and many LEFT JOIN
2019-02-22 18:05 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: Aggregate and many LEFT JOIN
2019-02-25 08:54 UTC kimaidou <kimaidou@gmail.com>
` Re: Aggregate and many LEFT JOIN
2019-02-25 09:44 UTC kimaidou <kimaidou@gmail.com>
` Re: Aggregate and many LEFT JOIN
2019-02-25 18:29 UTC Michael Lewis <mlewis@entrata.com>
` Re: Aggregate and many LEFT JOIN
2019-02-26 12:54 UTC kimaidou <kimaidou@gmail.com>
` Re: Aggregate and many LEFT JOIN
2019-02-26 13:51 UTC Justin Pryzby <pryzby@telsasoft.com>
` Re: Aggregate and many LEFT JOIN
2019-02-26 13:52 UTC Jeff Janes <jeff.janes@gmail.com>
[12+ messages in thread]
Massive parallel queue table causes index deterioration, but REINDEX fails with deadlocks.
2019-02-23 21:05 UTC Gunther <raj@gusw.net>
` Re: Massive parallel queue table causes index deterioration, but REINDEX fails with deadlocks.
2019-02-23 21:13 UTC Peter Geoghegan <pg@bowt.ie>
` Re: Massive parallel queue table causes index deterioration, but REINDEX fails with deadlocks.
2019-02-24 02:55 UTC Gunther <raj@gusw.net>
` Re: Massive parallel queue table causes index deterioration, but REINDEX fails with deadlocks.
2019-02-24 06:41 UTC David Rowley <david.rowley@2ndquadrant.com>
` Re: Massive parallel queue table causes index deterioration, but REINDEX fails with deadlocks.
2019-02-24 07:03 UTC Justin Pryzby <pryzby@telsasoft.com>
` Re: Massive parallel queue table causes index deterioration, but REINDEX fails with deadlocks.
2019-02-24 07:25 UTC Corey Huinker <corey.huinker@gmail.com>
` Re: Massive parallel queue table causes index deterioration, but REINDEX fails with deadlocks.
2019-02-24 17:45 UTC Gunther <raj@gusw.net>
` Re: Massive parallel queue table causes index deterioration, but REINDEX fails with deadlocks.
2019-02-24 20:20 UTC Justin Pryzby <pryzby@telsasoft.com>
` Re: Massive parallel queue table causes index deterioration, but REINDEX fails with deadlocks.
2019-02-24 20:41 UTC Peter Geoghegan <pg@bowt.ie>
` Re: Massive parallel queue table causes index deterioration, but REINDEX fails with deadlocks.
2019-02-24 21:34 UTC Corey Huinker <corey.huinker@gmail.com>
` Re: Massive parallel queue table causes index deterioration, but REINDEX fails with deadlocks.
2019-02-24 22:43 UTC Justin Pryzby <pryzby@telsasoft.com>
` Re: Massive parallel queue table causes index deterioration, but REINDEX fails with deadlocks.
2019-02-24 22:52 UTC Corey Huinker <corey.huinker@gmail.com>
` Re: Massive parallel queue table causes index deterioration, but REINDEX fails with deadlocks.
2019-02-24 23:33 UTC Jeff Janes <jeff.janes@gmail.com>
` Re: Massive parallel queue table causes index deterioration, but REINDEX fails with deadlocks.
2019-02-24 23:39 UTC Jeff Janes <jeff.janes@gmail.com>
` Re: Massive parallel queue table causes index deterioration, but REINDEX fails with deadlocks.
2019-02-25 03:06 UTC Gunther Schadow <gunther@pragmaticdata.com>
` Re: Massive parallel queue table causes index deterioration, but REINDEX fails with deadlocks.
2019-02-25 03:06 UTC Gunther <raj@gusw.net>
` Re: Massive parallel queue table causes index deterioration, but REINDEX fails with deadlocks.
2019-02-25 03:54 UTC Justin Pryzby <pryzby@telsasoft.com>
` Re: Massive parallel queue table causes index deterioration, but REINDEX fails with deadlocks.
2019-02-25 16:30 UTC Corey Huinker <corey.huinker@gmail.com>
` Re: Massive parallel queue table causes index deterioration, but REINDEX fails with deadlocks.
2019-02-25 20:30 UTC Jeff Janes <jeff.janes@gmail.com>
` Re: Massive parallel queue table causes index deterioration, but REINDEX fails with deadlocks.
2019-02-25 21:03 UTC Jeff Janes <jeff.janes@gmail.com>
` Re: Massive parallel queue table causes index deterioration, but REINDEX fails with deadlocks.
2019-02-25 21:07 UTC MichaelDBA <MichaelDBA@sqlexec.com>
[21+ messages in thread]
Idle backends outside a transaction holding onto large amounts of memory / swap space?
2019-02-25 10:36 UTC Tobias Gierke <tobias.gierke@code-sourcery.de>
` Re: Idle backends outside a transaction holding onto large amounts of memory / swap space?
2019-02-25 10:52 UTC Pavel Stehule <pavel.stehule@gmail.com>
[2+ messages in thread]
Slow query with aggregate and many LEFT JOINS
2019-02-22 15:36 UTC kimaidou <kimaidou@gmail.com>
` RE: Slow query with aggregate and many LEFT JOINS
2019-02-22 19:47 UTC Igor Neyman <ineyman@perceptron.com>
` RE: Slow query with aggregate and many LEFT JOINS
2019-02-22 19:53 UTC Igor Neyman <ineyman@perceptron.com>
[3+ messages in thread]
neither CPU nor IO bound, but throttled performance
2019-02-20 23:32 UTC Gunther <raj@gusw.net>
` Re: neither CPU nor IO bound, but throttled performance
2019-02-21 01:32 UTC Justin Pryzby <pryzby@telsasoft.com>
` Re: neither CPU nor IO bound, but throttled performance
2019-02-21 09:08 UTC Magnus Hagander <magnus@hagander.net>
` Re: neither CPU nor IO bound, but throttled performance
2019-02-21 15:59 UTC Gunther Schadow <gunther@pragmaticdata.com>
[4+ messages in thread]
How can sort performance be so different
2019-01-29 18:29 UTC Bob Jolliffe <bobjolliffe@gmail.com>
` Re: How can sort performance be so different
2019-01-29 18:33 UTC Pavel Stehule <pavel.stehule@gmail.com>
` Re: How can sort performance be so different
2019-01-29 18:36 UTC Saurabh Nanda <saurabhnanda@gmail.com>
` Re: How can sort performance be so different
2019-01-29 18:47 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: How can sort performance be so different
2019-01-30 11:57 UTC Bob Jolliffe <bobjolliffe@gmail.com>
` Re: How can sort performance be so different
2019-01-30 23:54 UTC Peter Geoghegan <pg@bowt.ie>
` Re: How can sort performance be so different
2019-01-31 13:29 UTC Bob Jolliffe <bobjolliffe@gmail.com>
` Re: How can sort performance be so different
2019-02-05 20:30 UTC Merlin Moncure <mmoncure@gmail.com>
` Re: How can sort performance be so different
2019-02-06 08:38 UTC Laurenz Albe <laurenz.albe@cybertec.at>
` Re: How can sort performance be so different
2019-02-18 15:49 UTC Bob Jolliffe <bobjolliffe@gmail.com>
` Re: How can sort performance be so different
2019-02-20 21:35 UTC Merlin Moncure <mmoncure@gmail.com>
` Re: How can sort performance be so different
2019-02-20 21:42 UTC Bob Jolliffe <bobjolliffe@gmail.com>
` Re: How can sort performance be so different
2019-02-20 22:25 UTC Peter Geoghegan <pg@bowt.ie>
` Re: How can sort performance be so different
2019-02-21 00:54 UTC Peter Geoghegan <pg@bowt.ie>
[14+ messages in thread]
Why isn't an index scan being used?
2019-02-20 00:10 UTC Abi Noda <a@abinoda.com>
` Re: Why isn't an index scan being used?
2019-02-20 00:51 UTC David Rowley <david.rowley@2ndquadrant.com>
` Re: Why isn't an index scan being used?
2019-02-20 00:59 UTC Abi Noda <a@abinoda.com>
` Re: Why isn't an index scan being used?
2019-02-20 03:00 UTC Andrew Gierth <andrew@tao11.riddles.org.uk>
` Re: Why isn't an index scan being used?
2019-02-20 04:29 UTC Michael Lewis <mlewis@entrata.com>
` Re: Why isn't an index scan being used?
2019-02-20 04:37 UTC Justin Pryzby <pryzby@telsasoft.com>
` Re: Why isn't an index scan being used?
2019-02-20 04:58 UTC Abi Noda <a@abinoda.com>
` Re: Why isn't an index scan being used?
2019-02-20 08:05 UTC Justin Pryzby <pryzby@telsasoft.com>
` Re: Why isn't an index scan being used?
2019-02-20 14:58 UTC Jeff Janes <jeff.janes@gmail.com>
[9+ messages in thread]
index on jsonb col with 2D array inside the json
2019-02-19 15:59 UTC Mariel Cherkassky <mariel.cherkassky@gmail.com>
` Re: index on jsonb col with 2D array inside the json
2019-02-19 16:28 UTC Michael Lewis <mlewis@entrata.com>
` Re: index on jsonb col with 2D array inside the json
2019-02-19 16:33 UTC Mariel Cherkassky <mariel.cherkassky@gmail.com>
` Re: index on jsonb col with 2D array inside the json
2019-02-19 16:41 UTC Michael Lewis <mlewis@entrata.com>
` Re: index on jsonb col with 2D array inside the json
2019-02-19 18:30 UTC Mariel Cherkassky <mariel.cherkassky@gmail.com>
[5+ messages in thread]
dsa_allocate() faliure
2018-01-29 16:19 UTC Rick Otten <rottenwindfish@gmail.com>
` Re: dsa_allocate() faliure
2018-01-29 16:37 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: dsa_allocate() faliure
2018-01-29 20:52 UTC Thomas Munro <thomas.munro@enterprisedb.com>
` Re: dsa_allocate() faliure
2018-01-29 21:35 UTC Rick Otten <rottenwindfish@gmail.com>
` Re: dsa_allocate() faliure
2018-05-23 04:10 UTC Sand Stone <sand.m.stone@gmail.com>
` Re: dsa_allocate() faliure
2018-05-23 04:44 UTC Thomas Munro <thomas.munro@enterprisedb.com>
` Re: dsa_allocate() faliure
2018-05-23 14:06 UTC Sand Stone <sand.m.stone@gmail.com>
` Re: dsa_allocate() faliure
2018-08-15 20:32 UTC Sand Stone <sand.m.stone@gmail.com>
` Re: dsa_allocate() faliure
2018-08-15 22:42 UTC Thomas Munro <thomas.munro@enterprisedb.com>
` Re: dsa_allocate() faliure
2018-08-25 14:46 UTC Sand Stone <sand.m.stone@gmail.com>
` Re: dsa_allocate() faliure
2018-08-29 04:44 UTC Sand Stone <sand.m.stone@gmail.com>
` Re: dsa_allocate() faliure
2018-10-05 02:16 UTC Thomas Munro <thomas.munro@enterprisedb.com>
` Re: dsa_allocate() faliure
2018-11-13 13:08 UTC Jakub Glapa <jakub.glapa@gmail.com>
` Re: dsa_allocate() faliure
2018-11-21 14:26 UTC Jakub Glapa <jakub.glapa@gmail.com>
` Re: dsa_allocate() faliure
2018-11-22 16:09 UTC Justin Pryzby <pryzby@telsasoft.com>
` Re: dsa_allocate() faliure
2018-11-23 14:31 UTC Jakub Glapa <jakub.glapa@gmail.com>
` Re: dsa_allocate() faliure
2018-11-23 16:10 UTC Justin Pryzby <pryzby@telsasoft.com>
` Re: dsa_allocate() faliure
2018-11-26 15:26 UTC Jakub Glapa <jakub.glapa@gmail.com>
` Re: dsa_allocate() faliure
2018-11-26 15:38 UTC Jakub Glapa <jakub.glapa@gmail.com>
` Re: dsa_allocate() faliure
2018-11-26 15:52 UTC Justin Pryzby <pryzby@telsasoft.com>
` Re: dsa_allocate() faliure
2018-11-26 16:00 UTC Jakub Glapa <jakub.glapa@gmail.com>
` Re: dsa_allocate() faliure
2018-11-26 18:45 UTC Alvaro Herrera <alvherre@2ndquadrant.com>
` Re: dsa_allocate() faliure
2018-11-27 03:00 UTC Thomas Munro <thomas.munro@enterprisedb.com>
` Re: dsa_allocate() faliure
2018-11-27 08:02 UTC Thomas Munro <thomas.munro@enterprisedb.com>
` Re: dsa_allocate() faliure
2018-11-30 19:20 UTC Jakub Glapa <jakub.glapa@gmail.com>
` Re: dsa_allocate() faliure
2018-11-30 20:46 UTC Justin Pryzby <pryzby@telsasoft.com>
` Re: dsa_allocate() faliure
2018-12-02 22:45 UTC Thomas Munro <thomas.munro@enterprisedb.com>
` RE: dsa_allocate() faliure
2019-01-24 14:44 UTC Arne Roland <A.Roland@index.de>
` RE: dsa_allocate() faliure
2019-01-28 13:50 UTC Arne Roland <A.Roland@index.de>
` Re: dsa_allocate() faliure
2019-01-28 18:56 UTC Thomas Munro <thomas.munro@enterprisedb.com>
` Re: dsa_allocate() faliure
2019-01-29 11:32 UTC Fabio Isabettini <fisabettini@voipfuture.com>
` Re: dsa_allocate() faliure
2019-01-30 03:13 UTC Thomas Munro <thomas.munro@enterprisedb.com>
` Re: dsa_allocate() faliure
2019-01-30 09:53 UTC Fabio Isabettini <fisabettini@voipfuture.com>
` RE: dsa_allocate() faliure
2019-01-31 18:19 UTC Arne Roland <A.Roland@index.de>
` Re: dsa_allocate() faliure
2019-02-01 18:08 UTC Justin Pryzby <pryzby@telsasoft.com>
` Re: dsa_allocate() faliure
2019-02-04 07:52 UTC Jakub Glapa <jakub.glapa@gmail.com>
` Re: dsa_allocate() faliure
2019-02-04 08:22 UTC Thomas Munro <thomas.munro@enterprisedb.com>
` RE: dsa_allocate() faliure
2019-02-04 20:31 UTC Arne Roland <A.Roland@index.de>
` Re: dsa_allocate() faliure
2019-02-04 21:47 UTC Justin Pryzby <pryzby@telsasoft.com>
` Re: dsa_allocate() faliure
2019-02-06 23:21 UTC Justin Pryzby <pryzby@telsasoft.com>
` Re: dsa_allocate() faliure
2019-02-07 10:10 UTC Jakub Glapa <jakub.glapa@gmail.com>
` Re: dsa_allocate() faliure
2019-02-07 17:49 UTC Thomas Munro <thomas.munro@enterprisedb.com>
` Re: dsa_allocate() faliure
2019-02-08 02:29 UTC Thomas Munro <thomas.munro@enterprisedb.com>
` Re: dsa_allocate() faliure
2019-02-09 10:21 UTC Robert Haas <robertmhaas@gmail.com>
` Re: dsa_allocate() faliure
2019-02-09 20:24 UTC Thomas Munro <thomas.munro@enterprisedb.com>
` Re: dsa_allocate() faliure
2019-02-09 21:06 UTC Thomas Munro <thomas.munro@enterprisedb.com>
` Re: dsa_allocate() faliure
2019-02-10 06:26 UTC Robert Haas <robertmhaas@gmail.com>
` Re: dsa_allocate() faliure
2019-02-10 06:40 UTC Robert Haas <robertmhaas@gmail.com>
` Re: dsa_allocate() faliure
2019-02-10 16:00 UTC Justin Pryzby <pryzby@telsasoft.com>
` Re: dsa_allocate() faliure
2019-02-10 16:11 UTC Sergei Kornilov <sk@zsrv.org>
` Re: dsa_allocate() faliure
2019-02-10 16:50 UTC Justin Pryzby <pryzby@telsasoft.com>
` Re: dsa_allocate() faliure
2019-02-10 22:45 UTC Thomas Munro <thomas.munro@enterprisedb.com>
` Re: dsa_allocate() faliure
2019-02-10 23:33 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: dsa_allocate() faliure
2019-02-11 00:02 UTC Justin Pryzby <pryzby@telsasoft.com>
` Re: dsa_allocate() faliure
2019-02-11 00:11 UTC Thomas Munro <thomas.munro@enterprisedb.com>
` Re: dsa_allocate() faliure
2019-02-11 00:24 UTC Thomas Munro <thomas.munro@enterprisedb.com>
` Re: dsa_allocate() faliure
2019-02-11 01:22 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: dsa_allocate() faliure
2019-02-13 00:52 UTC Thomas Munro <thomas.munro@enterprisedb.com>
` Re: dsa_allocate() faliure
2019-02-17 22:21 UTC Justin Pryzby <pryzby@telsasoft.com>
` Re: dsa_allocate() faliure
2019-02-18 09:11 UTC Jakub Glapa <jakub.glapa@gmail.com>
[60+ messages in thread]
Re: constraint exclusion with ineq condition (Re: server hardware tuning.)
2019-02-14 10:05 UTC Justin Pryzby <pryzby@telsasoft.com>
` Re: constraint exclusion with ineq condition (Re: server hardware tuning.)
2019-02-14 10:38 UTC suganthi Sekar <suganthi@uniphore.com>
` Re: constraint exclusion with ineq condition (Re: server hardware tuning.)
2019-02-14 10:40 UTC Justin Pryzby <pryzby@telsasoft.com>
` Re: constraint exclusion with ineq condition (Re: server hardware tuning.)
2019-02-14 10:49 UTC suganthi Sekar <suganthi@uniphore.com>
` Re: constraint exclusion with ineq condition (Re: server hardware tuning.)
2019-02-14 14:05 UTC Michael Lewis <mlewis@entrata.com>
` Re: constraint exclusion with ineq condition (Re: server hardware tuning.)
2019-02-14 14:35 UTC suganthi Sekar <suganthi@uniphore.com>
` Re: constraint exclusion with ineq condition (Re: server hardware tuning.)
2019-02-14 18:50 UTC Michael Lewis <mlewis@entrata.com>
` Re: constraint exclusion with ineq condition (Re: server hardware tuning.)
2019-02-15 05:09 UTC suganthi Sekar <suganthi@uniphore.com>
` Re: constraint exclusion with ineq condition (Re: server hardware tuning.)
2019-02-15 17:24 UTC Benedict Holland <benedict.m.holland@gmail.com>
` Re: constraint exclusion with ineq condition (Re: server hardware tuning.)
2019-02-16 22:04 UTC Justin Pryzby <pryzby@telsasoft.com>
[10+ messages in thread]
ERROR: unrecognized parameter "autovacuum_analyze_scale_factor"
2019-02-13 15:43 UTC Mariel Cherkassky <mariel.cherkassky@gmail.com>
` Re: ERROR: unrecognized parameter "autovacuum_analyze_scale_factor"
2019-02-13 16:13 UTC Alvaro Herrera <alvherre@2ndquadrant.com>
` Re: ERROR: unrecognized parameter "autovacuum_analyze_scale_factor"
2019-02-13 16:41 UTC Mariel Cherkassky <mariel.cherkassky@gmail.com>
` Re: ERROR: unrecognized parameter "autovacuum_analyze_scale_factor"
2019-02-13 16:54 UTC Alvaro Herrera <alvherre@2ndquadrant.com>
` Re: ERROR: unrecognized parameter "autovacuum_analyze_scale_factor"
2019-02-14 07:56 UTC Mariel Cherkassky <mariel.cherkassky@gmail.com>
` Re: ERROR: unrecognized parameter "autovacuum_analyze_scale_factor"
2019-02-15 13:39 UTC Alvaro Herrera <alvherre@2ndquadrant.com>
` Re: ERROR: unrecognized parameter "autovacuum_analyze_scale_factor"
2019-02-15 18:00 UTC Mariel Cherkassky <mariel.cherkassky@gmail.com>
[7+ messages in thread]
autovacuum big table taking hours and sometimes seconds
2019-02-06 10:29 UTC Mariel Cherkassky <mariel.cherkassky@gmail.com>
` Re: autovacuum big table taking hours and sometimes seconds
2019-02-06 11:16 UTC Laurenz Albe <laurenz.albe@cybertec.at>
` Re: autovacuum big table taking hours and sometimes seconds
2019-02-06 13:05 UTC David Rowley <david.rowley@2ndquadrant.com>
` Re: autovacuum big table taking hours and sometimes seconds
2019-02-06 13:34 UTC Mariel Cherkassky <mariel.cherkassky@gmail.com>
` Re: autovacuum big table taking hours and sometimes seconds
2019-02-06 13:36 UTC dangal <danielito.gallo@gmail.com>
` Re: autovacuum big table taking hours and sometimes seconds
2019-02-06 13:41 UTC Mariel Cherkassky <mariel.cherkassky@gmail.com>
` Re: autovacuum big table taking hours and sometimes seconds
2019-02-06 14:11 UTC MichaelDBA <MichaelDBA@sqlexec.com>
` Re: autovacuum big table taking hours and sometimes seconds
2019-02-06 14:12 UTC Jeff Janes <jeff.janes@gmail.com>
` Re: autovacuum big table taking hours and sometimes seconds
2019-02-06 14:42 UTC Mariel Cherkassky <mariel.cherkassky@gmail.com>
` Re: autovacuum big table taking hours and sometimes seconds
2019-02-06 18:49 UTC Jeff Janes <jeff.janes@gmail.com>
` Re: autovacuum big table taking hours and sometimes seconds
2019-02-06 22:33 UTC David Rowley <david.rowley@2ndquadrant.com>
` Re: autovacuum big table taking hours and sometimes seconds
2019-02-07 11:55 UTC Mariel Cherkassky <mariel.cherkassky@gmail.com>
` Re: autovacuum big table taking hours and sometimes seconds
2019-02-07 16:26 UTC Jeff Janes <jeff.janes@gmail.com>
` Re: autovacuum big table taking hours and sometimes seconds
2019-02-14 16:09 UTC Mariel Cherkassky <mariel.cherkassky@gmail.com>
` Re: autovacuum big table taking hours and sometimes seconds
2019-02-14 18:37 UTC Michael Lewis <mlewis@entrata.com>
` Re: autovacuum big table taking hours and sometimes seconds
2019-02-14 19:40 UTC Mariel Cherkassky <mariel.cherkassky@gmail.com>
` Re: autovacuum big table taking hours and sometimes seconds
2019-02-14 19:52 UTC Michael Lewis <mlewis@entrata.com>
` Re: autovacuum big table taking hours and sometimes seconds
2019-02-14 20:07 UTC Mariel Cherkassky <mariel.cherkassky@gmail.com>
` Re: autovacuum big table taking hours and sometimes seconds
2019-02-14 21:45 UTC Michael Lewis <mlewis@entrata.com>
` Re: autovacuum big table taking hours and sometimes seconds
2019-02-15 06:23 UTC Mariel Cherkassky <mariel.cherkassky@gmail.com>
` Re: autovacuum big table taking hours and sometimes seconds
2019-02-15 08:06 UTC Laurenz Albe <laurenz.albe@cybertec.at>
[21+ messages in thread]
JIT overhead slowdown
2019-01-18 14:12 UTC Luis Carril <luis.carril@swarm64.com>
` Re: JIT overhead slowdown
2019-01-18 16:42 UTC Andres Freund <andres@anarazel.de>
` Re: JIT overhead slowdown
2019-01-18 18:02 UTC Luis Carril <luis.carril@swarm64.com>
` Re: JIT overhead slowdown
2019-02-14 21:03 UTC Justin Pryzby <pryzby@telsasoft.com>
[4+ messages in thread]
Q on SQL Performance tuning
2019-01-27 08:43 UTC Bhupathi, Kaushik (CORP) <Kaushik.Bhupathi@ADP.com>
` Re: Q on SQL Performance tuning
2019-01-27 11:28 UTC legrand legrand <legrand_legrand@hotmail.com>
` Re: Q on SQL Performance tuning
2019-01-27 14:31 UTC Justin Pryzby <pryzby@telsasoft.com>
` Re: Q on SQL Performance tuning
2019-02-14 20:29 UTC Greg Stark <stark@mit.edu>
[4+ messages in thread]
partition pruning
2010-03-01 19:29 UTC Anj Adu <fotographs@gmail.com>
` Re: partition pruning
2010-03-04 22:40 UTC Robert Haas <robertmhaas@gmail.com>
` Re: partition pruning
2010-03-08 22:39 UTC Simon Riggs <simon@2ndQuadrant.com>
` Re: partition pruning
2019-02-14 12:37 UTC Laurenz Albe <laurenz.albe@cybertec.at>
` Re: partition pruning
2019-02-14 12:41 UTC suganthi Sekar <suganthi@uniphore.com>
` Re: partition pruning
2019-02-14 14:36 UTC Justin Pryzby <pryzby@telsasoft.com>
[6+ messages in thread]
Fw: server hardware tuning.
2019-02-04 09:57 UTC suganthi Sekar <suganthi@uniphore.com>
` Re: Fw: server hardware tuning.
2019-02-04 14:45 UTC Prince Pathria <prince.pathria@goevive.com>
` Re: server hardware tuning.
2019-02-14 09:38 UTC suganthi Sekar <suganthi@uniphore.com>
[3+ messages in thread]
understanding max_wal_size,wal_keep_segments and checkpoints
2019-02-13 08:34 UTC Mariel Cherkassky <mariel.cherkassky@gmail.com>
` Re: understanding max_wal_size,wal_keep_segments and checkpoints
2019-02-13 09:43 UTC Laurenz Albe <laurenz.albe@cybertec.at>
` Re: understanding max_wal_size,wal_keep_segments and checkpoints
2019-02-13 10:45 UTC Mariel Cherkassky <mariel.cherkassky@gmail.com>
` Re: understanding max_wal_size,wal_keep_segments and checkpoints
2019-02-13 11:23 UTC Laurenz Albe <laurenz.albe@cybertec.at>
[4+ messages in thread]
Partitioning Optimizer Questions and Issues
2019-02-08 11:13 UTC keith anderson <kwj.anderson@yahoo.co.uk>
` Re: Partitioning Optimizer Questions and Issues
2019-02-08 13:04 UTC Justin Pryzby <pryzby@telsasoft.com>
` Re: Partitioning Optimizer Questions and Issues
2019-02-11 08:05 UTC keith anderson <kwj.anderson@yahoo.co.uk>
[3+ messages in thread]
Re: slow to run query 5000 times
2019-02-09 17:16 UTC Justin Pryzby <pryzby@telsasoft.com>
` Re: slow to run query 5000 times
2019-02-09 20:23 UTC Andres Freund <andres@anarazel.de>
` Re: slow to run query 5000 times
2019-02-10 00:23 UTC Ricardo Martin Gomez <rimartingomez@hotmail.com>
[3+ messages in thread]
Transaction size and Wal2Json
2019-02-07 10:38 UTC Mai Peng <maily.peng@webedia-group.com>
` Re: Transaction size and Wal2Json
2019-02-07 10:45 UTC Peter Eisentraut <peter.eisentraut@2ndquadrant.com>
[2+ messages in thread]
Sv: Re: Fw: server hardware tuning.
2019-02-04 14:56 UTC Andreas Joseph Krogh <andreas@visena.com>
Setting effective_cache size
2019-01-31 07:30 UTC Nandakumar M <m.nanda92@gmail.com>
` Re: Setting effective_cache size
2019-01-31 07:34 UTC Nandakumar M <m.nanda92@gmail.com>
` Re: Setting effective_cache size
2019-01-31 11:57 UTC Laurenz Albe <laurenz.albe@cybertec.at>
[3+ messages in thread]
pgstattupple vs pg_total_relation_size
2019-01-30 10:41 UTC Mariel Cherkassky <mariel.cherkassky@gmail.com>
` Re: pgstattupple vs pg_total_relation_size
2019-01-30 13:19 UTC Tumasgiu Rossini <rossini.t@gmail.com>
` Re: pgstattupple vs pg_total_relation_size
2019-01-30 13:27 UTC Jehan-Guillaume (ioguix) de Rorthais <ioguix@free.fr>
` Re: pgstattupple vs pg_total_relation_size
2019-01-30 14:32 UTC Mariel Cherkassky <mariel.cherkassky@gmail.com>
` Re: pgstattupple vs pg_total_relation_size
2019-01-30 14:46 UTC Tom Lane <tgl@sss.pgh.pa.us>
[5+ messages in thread]
Will higher shared_buffers improve tpcb-like benchmarks?
2019-01-29 11:39 UTC Saurabh Nanda <saurabhnanda@gmail.com>
` Re: Will higher shared_buffers improve tpcb-like benchmarks?
2019-01-29 12:12 UTC Joe Mirabal <jmmirabal@gmail.com>
` Re: Will higher shared_buffers improve tpcb-like benchmarks?
2019-01-29 18:00 UTC Jeff Janes <jeff.janes@gmail.com>
` Re: Will higher shared_buffers improve tpcb-like benchmarks?
2019-01-29 18:10 UTC Saurabh Nanda <saurabhnanda@gmail.com>
` Re: Will higher shared_buffers improve tpcb-like benchmarks?
2019-01-30 03:50 UTC Saurabh Nanda <saurabhnanda@gmail.com>
[5+ messages in thread]
Interpreting shared_buffers setting
2019-01-29 12:32 UTC Bob Jolliffe <bobjolliffe@gmail.com>
` Re: Interpreting shared_buffers setting
2019-01-29 12:35 UTC Thomas Markus <t.markus@proventis.net>
` Re: Interpreting shared_buffers setting
2019-01-29 13:07 UTC Andrew Gierth <andrew@tao11.riddles.org.uk>
` Re: Interpreting shared_buffers setting
2019-01-29 15:42 UTC Bob Jolliffe <bobjolliffe@gmail.com>
` Re: Interpreting shared_buffers setting
2019-01-29 18:31 UTC Jerry Sievers <gsievers19@comcast.net>
` Re: Interpreting shared_buffers setting
2019-01-29 18:40 UTC Jerry Sievers <gsievers19@comcast.net>
[6+ messages in thread]
[next (older)]
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox