pg.ddx.io pgsql-performance@postgresql.org mailing list archive
help / color / mirror / Atom feedRe: 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]
Benchmarking: How to identify bottleneck (limiting factor) and achieve "linear scalability"?
2019-01-23 19:16 UTC Saurabh Nanda <saurabhnanda@gmail.com>
` Re: Benchmarking: How to identify bottleneck (limiting factor) and achieve "linear scalability"?
2019-01-25 07:17 UTC Saurabh Nanda <saurabhnanda@gmail.com>
` Re: Benchmarking: How to identify bottleneck (limiting factor) and achieve "linear scalability"?
2019-01-26 11:10 UTC Saurabh Nanda <saurabhnanda@gmail.com>
` Re: Benchmarking: How to identify bottleneck (limiting factor) and achieve "linear scalability"?
2019-01-27 07:39 UTC Saurabh Nanda <saurabhnanda@gmail.com>
` Re: Benchmarking: How to identify bottleneck (limiting factor) and achieve "linear scalability"?
2019-01-27 16:04 UTC Justin Pryzby <pryzby@telsasoft.com>
` Re: Benchmarking: How to identify bottleneck (limiting factor) and achieve "linear scalability"?
2019-01-27 16:38 UTC Saurabh Nanda <saurabhnanda@gmail.com>
` Re: Benchmarking: How to identify bottleneck (limiting factor) and achieve "linear scalability"?
2019-01-27 17:48 UTC Jeff Janes <jeff.janes@gmail.com>
` Re: Benchmarking: How to identify bottleneck (limiting factor) and achieve "linear scalability"?
2019-01-27 19:41 UTC Jeff Janes <jeff.janes@gmail.com>
` Re: Benchmarking: How to identify bottleneck (limiting factor) and achieve "linear scalability"?
2019-01-28 04:52 UTC Saurabh Nanda <saurabhnanda@gmail.com>
` Re: Benchmarking: How to identify bottleneck (limiting factor) and achieve "linear scalability"?
2019-01-28 04:59 UTC Saurabh Nanda <saurabhnanda@gmail.com>
` Re: Benchmarking: How to identify bottleneck (limiting factor) and achieve "linear scalability"?
2019-01-28 05:03 UTC Saurabh Nanda <saurabhnanda@gmail.com>
` Re: Benchmarking: How to identify bottleneck (limiting factor) and achieve "linear scalability"?
2019-01-28 14:03 UTC Saurabh Nanda <saurabhnanda@gmail.com>
` Re: Benchmarking: How to identify bottleneck (limiting factor) and achieve "linear scalability"?
2019-01-28 14:22 UTC Nicolas Charles <nicolas.charles@normation.com>
` Re: Benchmarking: How to identify bottleneck (limiting factor) and achieve "linear scalability"?
2019-01-28 15:55 UTC Saurabh Nanda <saurabhnanda@gmail.com>
` Re: Benchmarking: How to identify bottleneck (limiting factor) and achieve "linear scalability"?
2019-01-28 16:06 UTC Nicolas Charles <nicolas.charles@normation.com>
` Re: Benchmarking: How to identify bottleneck (limiting factor) and achieve "linear scalability"?
2019-01-28 16:35 UTC Saurabh Nanda <saurabhnanda@gmail.com>
` Re: Benchmarking: How to identify bottleneck (limiting factor) and achieve "linear scalability"?
2019-01-28 16:56 UTC Saurabh Nanda <saurabhnanda@gmail.com>
` Re: Benchmarking: How to identify bottleneck (limiting factor) and achieve "linear scalability"?
2019-01-29 01:44 UTC Saurabh Nanda <saurabhnanda@gmail.com>
` Re: Benchmarking: How to identify bottleneck (limiting factor) and achieve "linear scalability"?
2019-01-29 04:48 UTC Saurabh Nanda <saurabhnanda@gmail.com>
` Re: Benchmarking: How to identify bottleneck (limiting factor) and achieve "linear scalability"?
2019-01-29 06:15 UTC Saurabh Nanda <saurabhnanda@gmail.com>
` Re: Benchmarking: How to identify bottleneck (limiting factor) and achieve "linear scalability"?
2019-01-29 09:14 UTC Nicolas Charles <nicolas.charles@normation.com>
` Re: Benchmarking: How to identify bottleneck (limiting factor) and achieve "linear scalability"?
2019-01-29 15:42 UTC Jeff Janes <jeff.janes@gmail.com>
[22+ messages in thread]
pg_locks - what is a virtualxid locktype
2019-01-29 08:57 UTC Mariel Cherkassky <mariel.cherkassky@gmail.com>
` Re: pg_locks - what is a virtualxid locktype
2019-01-29 09:33 UTC Shreeyansh Dba <shreeyansh2014@gmail.com>
` Re: pg_locks - what is a virtualxid locktype
2019-01-29 15:12 UTC Alvaro Herrera <alvherre@2ndquadrant.com>
[3+ messages in thread]
upgrade from 9.6 to 10/11
2019-01-28 10:04 UTC Mariel Cherkassky <mariel.cherkassky@gmail.com>
` Re: upgrade from 9.6 to 10/11
2019-01-28 10:20 UTC Laurenz Albe <laurenz.albe@cybertec.at>
` Re: upgrade from 9.6 to 10/11
2019-01-28 15:43 UTC Justin Pryzby <pryzby@telsasoft.com>
[3+ messages in thread]
Zero throughput on a query on a very large table.
2019-01-25 05:20 UTC ldh@laurent-hasson.com <ldh@laurent-hasson.com>
` Re: Zero throughput on a query on a very large table.
2019-01-25 05:54 UTC Andreas Kretschmer <andreas@a-kretschmer.de>
` Re: Zero throughput on a query on a very large table.
2019-01-25 06:24 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: Zero throughput on a query on a very large table.
2019-01-25 06:55 UTC David Rowley <david.rowley@2ndquadrant.com>
` RE: Zero throughput on a query on a very large table.
2019-01-25 17:47 UTC ldh@laurent-hasson.com <ldh@laurent-hasson.com>
` Re: Zero throughput on a query on a very large table.
2019-01-25 18:00 UTC ldh@laurent-hasson.com <ldh@laurent-hasson.com>
` Re: Zero throughput on a query on a very large table.
2019-01-25 18:10 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: Zero throughput on a query on a very large table.
2019-01-25 18:20 UTC ldh@laurent-hasson.com <ldh@laurent-hasson.com>
` Re: Zero throughput on a query on a very large table.
2019-01-25 18:29 UTC ldh@laurent-hasson.com <ldh@laurent-hasson.com>
` Re: Zero throughput on a query on a very large table.
2019-01-25 18:34 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: Zero throughput on a query on a very large table.
2019-01-25 18:36 UTC ldh@laurent-hasson.com <ldh@laurent-hasson.com>
` Re: Zero throughput on a query on a very large table.
2019-01-25 19:06 UTC ldh@laurent-hasson.com <ldh@laurent-hasson.com>
` Re: Zero throughput on a query on a very large table.
2019-01-25 19:24 UTC ldh@laurent-hasson.com <ldh@laurent-hasson.com>
` Re: Zero throughput on a query on a very large table.
2019-01-25 20:04 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: Zero throughput on a query on a very large table.
2019-01-25 20:31 UTC ldh@laurent-hasson.com <ldh@laurent-hasson.com>
[15+ messages in thread]
SELECT performance drop
2019-01-22 20:04 UTC Jan Nielsen <jan.sture.nielsen@gmail.com>
` Re: SELECT performance drop
2019-01-22 21:00 UTC Jan Nielsen <jan.sture.nielsen@gmail.com>
` Re: SELECT performance drop
2019-01-22 21:55 UTC legrand legrand <legrand_legrand@hotmail.com>
` Re: SELECT performance drop
2019-01-22 22:28 UTC Jan Nielsen <jan.sture.nielsen@gmail.com>
` Re: SELECT performance drop
2019-01-23 13:50 UTC Jim Finnerty <jfinnert@amazon.com>
` Re: SELECT performance drop
2019-01-23 17:28 UTC Jan Nielsen <jan.sture.nielsen@gmail.com>
` RE:SELECT performance drop
2019-01-23 19:37 UTC legrand legrand <legrand_legrand@hotmail.com>
` Re: SELECT performance drop
2019-01-23 22:41 UTC Laurenz Albe <laurenz.albe@cybertec.at>
` Re: SELECT performance drop
2019-01-24 16:52 UTC Jan Nielsen <jan.sture.nielsen@gmail.com>
` Re: SELECT performance drop
2019-01-24 18:04 UTC Jan Nielsen <jan.sture.nielsen@gmail.com>
[10+ messages in thread]
Parallel stats in execution plans
2019-01-16 11:31 UTC David Conlin <dc345@cantab.net>
` Re: Parallel stats in execution plans
2019-01-24 08:18 UTC David Conlin <dc345@cantab.net>
` Re: Parallel stats in execution plans
2019-01-24 11:55 UTC David Rowley <david.rowley@2ndquadrant.com>
[3+ messages in thread]
ANALYZE accuracy problems for n_distinct, and a solution
2019-01-22 21:13 UTC Jim Finnerty <jfinnert@amazon.com>
Memory and hard ware calculation :
2019-01-21 11:24 UTC Rangaraj G <rangaraj@uniphore.com>
` Re: Memory and hard ware calculation :
2019-01-21 17:43 UTC Cleiton Luiz Domazak <cleitondomazak@gmail.com>
` Re: Memory and hard ware calculation :
2019-01-22 08:11 UTC Fabio Pardi <f.pardi@portavita.eu>
` RE: Memory and hard ware calculation :
2019-01-22 12:54 UTC Rangaraj G <rangaraj@uniphore.com>
` Re: Memory and hard ware calculation :
2019-01-22 20:05 UTC Ron <ronljohnsonjr@gmail.com>
[5+ messages in thread]
Very long query planning times for database with lots of partitions
2019-01-22 13:44 UTC Mickael van der Beek <mickael@woorank.com>
` Re: Very long query planning times for database with lots of partitions
2019-01-22 14:02 UTC Justin Pryzby <pryzby@telsasoft.com>
` RE: Very long query planning times for database with lots of partitions
2019-01-22 14:07 UTC Steven Winfield <Steven.Winfield@cantabcapital.com>
` Re: Very long query planning times for database with lots of partitions
2019-01-22 15:24 UTC Mickael van der Beek <mickael@woorank.com>
[4+ 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