pg.ddx.io pgsql-performance@postgresql.org mailing list archive
help / color / mirror / Atom feed[PATCH v1] explain: show index_total_cost
2020-01-03 15:53 UTC Justin Pryzby <pryzbyj@telsasoft.com>
Merge join doesn't seem to break early when I (and planner) think it should - 10.4
2019-12-26 20:07 UTC Timothy Garnett <tgarnett@panjiva.com>
` Re: Merge join doesn't seem to break early when I (and planner) think it should - 10.4
2019-12-27 16:52 UTC Jeff Janes <jeff.janes@gmail.com>
[2+ messages in thread]
How to set parallel_tuple_cost
2019-12-20 18:03 UTC Jeff Janes <jeff.janes@gmail.com>
` Re: How to set parallel_tuple_cost
2019-12-20 18:42 UTC Laurenz Albe <laurenz.albe@cybertec.at>
` Re: How to set parallel_tuple_cost
2019-12-20 18:58 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: How to set parallel_tuple_cost
2019-12-21 00:24 UTC Andres Freund <andres@anarazel.de>
` Re: How to set parallel_tuple_cost
2019-12-21 01:37 UTC Jeff Janes <jeff.janes@gmail.com>
[5+ messages in thread]
Consecutive Query Executions with Increasing Execution Time
2019-12-16 05:59 UTC Shijia Wei <shijiawei@utexas.edu>
` Re: Consecutive Query Executions with Increasing Execution Time
2019-12-16 08:03 UTC Olivier Gautherot <ogautherot@gautherot.net>
` Re: Consecutive Query Executions with Increasing Execution Time
2019-12-16 09:51 UTC Shijia Wei <shijiawei@utexas.edu>
` Re: Consecutive Query Executions with Increasing Execution Time
2019-12-16 10:17 UTC Olivier Gautherot <ogautherot@gautherot.net>
` Re: Consecutive Query Executions with Increasing Execution Time
2019-12-16 13:25 UTC Laurenz Albe <laurenz.albe@cybertec.at>
` Re: Consecutive Query Executions with Increasing Execution Time
2019-12-16 13:50 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: Consecutive Query Executions with Increasing Execution Time
2019-12-16 17:28 UTC Shijia Wei <shijiawei@utexas.edu>
` Re: Consecutive Query Executions with Increasing Execution Time
2019-12-16 20:39 UTC Peter Geoghegan <pg@bowt.ie>
` Re: Consecutive Query Executions with Increasing Execution Time
2019-12-16 20:50 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: Consecutive Query Executions with Increasing Execution Time
2019-12-16 22:08 UTC Nicolas Charles <nicolas.charles@normation.com>
` Re: Consecutive Query Executions with Increasing Execution Time
2019-12-16 22:48 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: Consecutive Query Executions with Increasing Execution Time
2019-12-17 00:53 UTC Sam Gendler <sgendler@ideasculptor.com>
` Re: Consecutive Query Executions with Increasing Execution Time
2019-12-17 04:04 UTC Andres Freund <andres@anarazel.de>
` Re: Consecutive Query Executions with Increasing Execution Time
2019-12-17 13:08 UTC Laurenz Albe <laurenz.albe@cybertec.at>
` Re: Consecutive Query Executions with Increasing Execution Time
2019-12-17 16:11 UTC Jeff Janes <jeff.janes@gmail.com>
` Re: Consecutive Query Executions with Increasing Execution Time
2019-12-18 12:17 UTC Laurenz Albe <laurenz.albe@cybertec.at>
` Re: Consecutive Query Executions with Increasing Execution Time
2019-12-18 13:44 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: Consecutive Query Executions with Increasing Execution Time
2019-12-20 05:21 UTC Shijia Wei <shijiawei@utexas.edu>
[18+ messages in thread]
How to prevent POSTGRES killing linux system from accepting too much inserts?
2019-12-18 09:53 UTC =?utf-8?B?SmFtZXMo546L5petKQ==?= <wangxu@gu360.com>
` Re: How to prevent POSTGRES killing linux system from accepting too much inserts?
2019-12-18 18:07 UTC Steven Lembark <lembark@wrkhors.com>
` Re: How to prevent POSTGRES killing linux system from accepting too much inserts?
2019-12-18 18:34 UTC Merlin Moncure <mmoncure@gmail.com>
` Re: How to prevent POSTGRES killing linux system from accepting too much inserts?
2019-12-18 19:09 UTC Jeff Janes <jeff.janes@gmail.com>
[4+ messages in thread]
weird long time query
2019-12-17 02:58 UTC Kaijiang Chen <chenkaijiang@gmail.com>
` Re: weird long time query
2019-12-17 11:08 UTC Pavel Stehule <pavel.stehule@gmail.com>
` Re: weird long time query
2019-12-17 17:04 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: weird long time query
2019-12-18 03:23 UTC Kaijiang Chen <chenkaijiang@gmail.com>
` Fwd: weird long time query
2019-12-18 03:25 UTC Kaijiang Chen <chenkaijiang@gmail.com>
` Re: Fwd: weird long time query
2019-12-18 14:06 UTC hubert depesz lubaczewski <depesz@depesz.com>
` Re: Fwd: weird long time query
2019-12-18 16:14 UTC Kaijiang Chen <chenkaijiang@gmail.com>
` Re: Fwd: weird long time query
2019-12-18 16:23 UTC hubert depesz lubaczewski <depesz@depesz.com>
` Re: Fwd: weird long time query
2019-12-18 16:30 UTC Tom Lane <tgl@sss.pgh.pa.us>
[9+ messages in thread]
shared memory size during upgrade pgsql with partitions
2019-12-17 20:03 UTC =?iso-8859-2?Q?Piotr_W=B3odarczyk?= <piotr.wlodarczyk@gnb.pl>
` Re: shared memory size during upgrade pgsql with partitions (max_locks_per_transaction)
2019-12-18 04:01 UTC Justin Pryzby <pryzby@telsasoft.com>
` Re: shared memory size during upgrade pgsql with partitions (max_locks_per_transaction)
2019-12-18 09:16 UTC =?iso-8859-2?Q?Piotr_W=B3odarczyk?= <piotr.wlodarczyk@gnb.pl>
[3+ messages in thread]
performance degredation after upgrade from 9.6 to 12
2019-11-24 12:53 UTC Mariel Cherkassky <mariel.cherkassky@gmail.com>
` Re: performance degredation after upgrade from 9.6 to 12
2019-11-24 13:15 UTC Thomas Poty <thomas.poty@gmail.com>
` Re: performance degredation after upgrade from 9.6 to 12
2019-11-24 13:19 UTC Andrew Zakharov <Andrew898@mail.ru>
` Re: performance degredation after upgrade from 9.6 to 12
2019-11-24 13:51 UTC Mariel Cherkassky <mariel.cherkassky@gmail.com>
` Re: performance degredation after upgrade from 9.6 to 12
2019-11-24 15:22 UTC Jeff Janes <jeff.janes@gmail.com>
` Re: performance degredation after upgrade from 9.6 to 12
2019-11-24 15:30 UTC Jeff Janes <jeff.janes@gmail.com>
` Re: performance degredation after upgrade from 9.6 to 12
2019-11-24 18:05 UTC Mariel Cherkassky <mariel.cherkassky@gmail.com>
` Re: performance degredation after upgrade from 9.6 to 12
2019-11-24 20:00 UTC John Felix <johnfelix@zeelandnet.nl>
` Re: performance degredation after upgrade from 9.6 to 12
2019-11-24 20:50 UTC Jeff Janes <jeff.janes@gmail.com>
` Re: performance degredation after upgrade from 9.6 to 12
2019-11-24 21:49 UTC Mariel Cherkassky <mariel.cherkassky@gmail.com>
` Re: performance degredation after upgrade from 9.6 to 12
2019-12-03 21:13 UTC Andres Freund <andres@anarazel.de>
` Re: performance degredation after upgrade from 9.6 to 12
2019-12-16 11:48 UTC Mariel Cherkassky <mariel.cherkassky@gmail.com>
` RE: performance degredation after upgrade from 9.6 to 12
2019-12-16 12:27 UTC Andrew Zakharov <Andrew898@mail.ru>
` Re: performance degredation after upgrade from 9.6 to 12
2019-12-16 13:01 UTC Mariel Cherkassky <mariel.cherkassky@gmail.com>
` Re: performance degredation after upgrade from 9.6 to 12
2019-12-16 17:29 UTC Pavel Stehule <pavel.stehule@gmail.com>
[15+ messages in thread]
Legal disclaimers on emails to this group
2019-12-06 18:42 UTC Craig James <cjames@emolecules.com>
` Re: Legal disclaimers on emails to this group
2019-12-06 19:27 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: Legal disclaimers on emails to this group
2019-12-06 22:42 UTC Tim Cross <theophilusx@gmail.com>
` Re: Legal disclaimers on emails to this group
2019-12-07 12:10 UTC Jean-David Beyer <jeandavid8@verizon.net>
` RE: Legal disclaimers on emails to this group
2019-12-09 23:05 UTC Mike Schanne <mschanne@kns.com>
` Re: Legal disclaimers on emails to this group
2019-12-12 14:49 UTC Moreno Andreo <moreno.andreo@evolu-s.it>
` Re: Legal disclaimers on emails to this group
2019-12-12 15:03 UTC Moreno Andreo <moreno.andreo@evolu-s.it>
[7+ messages in thread]
unexpected result for wastedbytes query after vacuum full
2019-12-06 17:18 UTC Mike Schanne <mschanne@kns.com>
` Re: unexpected result for wastedbytes query after vacuum full
2019-12-06 23:28 UTC Justin Pryzby <pryzby@telsasoft.com>
` RE: unexpected result for wastedbytes query after vacuum full
2019-12-09 23:06 UTC Mike Schanne <mschanne@kns.com>
` Re: unexpected result for wastedbytes query after vacuum full
2019-12-10 16:43 UTC Guillaume Lelarge <guillaume@lelarge.info>
` Re: unexpected result for wastedbytes query after vacuum full
2019-12-10 19:48 UTC Jeff Janes <jeff.janes@gmail.com>
` Re: unexpected result for wastedbytes query after vacuum full
2019-12-11 15:23 UTC Guillaume Lelarge <guillaume@lelarge.info>
[6+ messages in thread]
Logical replication performance
2019-11-29 16:06 UTC Florian Philippon <florian.philippon@doctolib.com>
` Re: Logical replication performance
2019-11-29 16:25 UTC Flavio Henrique Araque Gurgel <fhagur@gmail.com>
` Re: Logical replication performance
2019-12-09 22:31 UTC Jeff Janes <jeff.janes@gmail.com>
[3+ messages in thread]
Re: How to run in parallel in Postgres, EXECUTE_PARALLEL
2019-12-08 18:14 UTC Lars Aksel Opsahl <Lars.Opsahl@nibio.no>
` Re: How to run in parallel in Postgres, EXECUTE_PARALLEL
2019-12-08 20:04 UTC Joe Conway <mail@joeconway.com>
` Re: How to run in parallel in Postgres, EXECUTE_PARALLEL
2019-12-08 21:59 UTC Lars Aksel Opsahl <Lars.Opsahl@nibio.no>
[3+ messages in thread]
query that canceled isnt logged
2019-12-08 13:08 UTC Mariel Cherkassky <mariel.cherkassky@gmail.com>
` Re: query that canceled isnt logged
2019-12-08 15:05 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: query that canceled isnt logged
2019-12-08 15:18 UTC Mariel Cherkassky <mariel.cherkassky@gmail.com>
` Re: query that canceled isnt logged
2019-12-08 15:23 UTC Mariel Cherkassky <mariel.cherkassky@gmail.com>
` Re: query that canceled isnt logged
2019-12-08 15:42 UTC Tom Lane <tgl@sss.pgh.pa.us>
[5+ messages in thread]
How to run in parallel in Postgres
2019-12-05 12:10 UTC Lars Aksel Opsahl <Lars.Opsahl@nibio.no>
` Re: How to run in parallel in Postgres
2019-12-05 16:42 UTC Laurenz Albe <laurenz.albe@cybertec.at>
` Re: How to run in parallel in Postgres
2019-12-06 08:39 UTC Lars Aksel Opsahl <Lars.Opsahl@nibio.no>
` Re: How to run in parallel in Postgres
2019-12-07 01:23 UTC Ondrej Ivanič <ondrej.ivanic@gmail.com>
` Re: How to run in parallel in Postgres
2019-12-07 01:25 UTC Justin Pryzby <pryzby@telsasoft.com>
` Re: How to run in parallel in Postgres
2019-12-07 11:17 UTC Lars Aksel Opsahl <Lars.Opsahl@nibio.no>
` Re: How to run in parallel in Postgres
2019-12-07 11:27 UTC Lars Aksel Opsahl <Lars.Opsahl@nibio.no>
[7+ messages in thread]
autovacuum locking question
2019-12-05 17:46 UTC Mike Schanne <mschanne@kns.com>
` Re: autovacuum locking question
2019-12-05 22:49 UTC Michael Lewis <mlewis@entrata.com>
` RE: autovacuum locking question
2019-12-05 23:18 UTC Mike Schanne <mschanne@kns.com>
` Re: autovacuum locking question
2019-12-05 23:49 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: autovacuum locking question
2019-12-05 23:55 UTC Jeff Janes <jeff.janes@gmail.com>
` RE: autovacuum locking question
2019-12-06 15:46 UTC Mike Schanne <mschanne@kns.com>
` RE: autovacuum locking question
2019-12-06 15:55 UTC Mike Schanne <mschanne@kns.com>
` Re: autovacuum locking question
2019-12-06 17:12 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: autovacuum locking question
2019-12-06 17:19 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: autovacuum locking question
2019-12-06 17:47 UTC Jeff Janes <jeff.janes@gmail.com>
` Re: autovacuum locking question
2019-12-06 17:49 UTC Justin Pryzby <pryzby@telsasoft.com>
` Re: autovacuum locking question
2019-12-06 17:50 UTC MichaelDBA <MichaelDBA@sqlexec.com>
` Re: autovacuum locking question
2019-12-07 00:59 UTC Jeff Janes <jeff.janes@gmail.com>
[13+ messages in thread]
threads (Re: Legal disclaimers on emails to this group)
2019-12-06 21:55 UTC Justin Pryzby <pryzby@telsasoft.com>
Postgres backup tool recommendations for multi-terabyte database in Google Cloud
2019-12-05 17:47 UTC Craig Jackson <craig.jackson@broadcom.com>
` Re: Postgres backup tool recommendations for multi-terabyte database in Google Cloud
2019-12-05 19:51 UTC Craig James <cjames@emolecules.com>
` Re: Postgres backup tool recommendations for multi-terabyte database in Google Cloud
2019-12-05 21:05 UTC Craig Jackson <craig.jackson@broadcom.com>
` Re: Postgres backup tool recommendations for multi-terabyte database in Google Cloud
2019-12-05 21:08 UTC Nikolay Samokhvalov <samokhvalov@gmail.com>
[4+ messages in thread]
Make recently inserted/updated records available in the buffer/cache
2019-12-02 17:03 UTC Sachin Divekar <ssd532@gmail.com>
` Re: Make recently inserted/updated records available in the buffer/cache
2019-12-02 17:13 UTC Hüseyin Demir <demirhuseyinn.94@gmail.com>
` Re: Make recently inserted/updated records available in the buffer/cache
2019-12-02 17:17 UTC MichaelDBA <MichaelDBA@sqlexec.com>
` Re: Make recently inserted/updated records available in the buffer/cache
2019-12-03 17:29 UTC Michael Lewis <mlewis@entrata.com>
` Re: Make recently inserted/updated records available in the buffer/cache
2019-12-03 17:32 UTC MichaelDBA <MichaelDBA@sqlexec.com>
` Re: Make recently inserted/updated records available in the buffer/cache
2019-12-03 18:45 UTC Sachin Divekar <ssd532@gmail.com>
` Re: Make recently inserted/updated records available in the buffer/cache
2019-12-03 18:58 UTC Michael Lewis <mlewis@entrata.com>
[7+ messages in thread]
[External] Join queries slow with predicate, limit, and ordering
2019-12-02 12:43 UTC Aufar Gilbran <aufar.gilbran@grab.com>
` Re: [External] Join queries slow with predicate, limit, and ordering
2019-12-03 00:38 UTC Jeff Janes <jeff.janes@gmail.com>
` Re: [External] Join queries slow with predicate, limit, and ordering
2019-12-03 07:50 UTC Aufar Gilbran <aufar.gilbran@grab.com>
[3+ messages in thread]
Considerable performance downgrade of v11 and 12 on Windows
2019-11-29 10:04 UTC Eugene Podshivalov <yaugenka@gmail.com>
` Re: Considerable performance downgrade of v11 and 12 on Windows
2019-11-29 10:36 UTC Thomas Kellerer <spam_eater@gmx.net>
` Re: Considerable performance downgrade of v11 and 12 on Windows
2019-11-29 10:47 UTC Eugene Podshivalov <yaugenka@gmail.com>
` Re: Considerable performance downgrade of v11 and 12 on Windows
2019-11-29 12:04 UTC Laurenz Albe <laurenz.albe@cybertec.at>
` Re: Considerable performance downgrade of v11 and 12 on Windows
2019-11-29 12:22 UTC Eugene Podshivalov <yaugenka@gmail.com>
` Re: Considerable performance downgrade of v11 and 12 on Windows
2019-11-30 19:47 UTC Eugene Podshivalov <yaugenka@gmail.com>
` Re: Considerable performance downgrade of v11 and 12 on Windows
2019-12-02 09:04 UTC Laurenz Albe <laurenz.albe@cybertec.at>
` Re: Considerable performance downgrade of v11 and 12 on Windows
2019-12-02 19:03 UTC Eugene Podshivalov <yaugenka@gmail.com>
[8+ messages in thread]
Postgresql planning time too high
2019-11-22 11:21 UTC Sterpu Victor <victor@caido.ro>
` RE: Postgresql planning time too high
2019-11-22 11:35 UTC Fırat Güleç <firat.gulec@hepsijet.com>
` Re: Postgresql planning time too high
2019-11-22 12:22 UTC Luís Roberto Weck <luisroberto@siscobra.com.br>
` Re: Postgresql planning time too high
2019-11-22 19:36 UTC Tomas Vondra <tomas.vondra@2ndquadrant.com>
[4+ messages in thread]
Hash Join over Nested Loop
2019-11-22 17:33 UTC Luís Roberto Weck <luisroberto@siscobra.com.br>
` Re: Hash Join over Nested Loop
2019-11-22 17:43 UTC Luís Roberto Weck <luisroberto@siscobra.com.br>
` Re: Hash Join over Nested Loop
2019-11-22 17:55 UTC Pavel Stehule <pavel.stehule@gmail.com>
` Re: Hash Join over Nested Loop
2019-11-22 18:48 UTC Luís Roberto Weck <luisroberto@siscobra.com.br>
` Re: Hash Join over Nested Loop
2019-11-22 18:54 UTC Pavel Stehule <pavel.stehule@gmail.com>
[5+ messages in thread]
Re[4]: Postgresql planning time too high
2019-11-22 12:25 UTC Sterpu Victor <victor@caido.ro>
` Re[4]: Postgresql planning time too high
2019-11-22 12:44 UTC Sterpu Victor <victor@caido.ro>
` Re[4]: Postgresql planning time too high
2019-11-22 13:45 UTC Sterpu Victor <victor@caido.ro>
` Re[4]: Postgresql planning time too high
2019-11-22 14:06 UTC Sterpu Victor <victor@caido.ro>
` Re: Re[4]: Postgresql planning time too high
2019-11-22 14:29 UTC Pavel Stehule <pavel.stehule@gmail.com>
` Re: Re[4]: Postgresql planning time too high
2019-11-22 18:13 UTC Michael Lewis <mlewis@entrata.com>
[6+ messages in thread]
Re[2]: Postgresql planning time too high
2019-11-22 11:44 UTC Sterpu Victor <victor@caido.ro>
` Re[2]: Postgresql planning time too high
2019-11-22 11:46 UTC Sterpu Victor <victor@caido.ro>
` RE: Re[2]: Postgresql planning time too high
2019-11-22 12:05 UTC Fırat Güleç <firat.gulec@hepsijet.com>
` Re: Re[2]: Postgresql planning time too high
2019-11-22 12:59 UTC Pavel Stehule <pavel.stehule@gmail.com>
[4+ messages in thread]
Re[3]: Postgresql planning time too high
2019-11-22 12:50 UTC Sterpu Victor <victor@caido.ro>
[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