pg.ddx.io pgsql-performance@postgresql.org mailing list archive
help / color / mirror / Atom feedincreased max_parallel_workers_per_gather results in fewer workers?
2020-06-03 20:04 UTC Philip Semanchuk <philip@americanefficient.com>
` Re: increased max_parallel_workers_per_gather results in fewer workers?
2020-06-03 21:15 UTC Justin Pryzby <pryzby@telsasoft.com>
` Re: increased max_parallel_workers_per_gather results in fewer workers?
2020-06-03 22:23 UTC Philip Semanchuk <philip@americanefficient.com>
` Re: increased max_parallel_workers_per_gather results in fewer workers?
2020-06-03 22:36 UTC Justin Pryzby <pryzby@telsasoft.com>
` Re: increased max_parallel_workers_per_gather results in fewer workers?
2020-06-04 06:28 UTC Sebastian Dressler <sebastian@swarm64.com>
` Re: increased max_parallel_workers_per_gather results in fewer workers?
2020-06-04 06:41 UTC Luis Carril <luis.carril@swarm64.com>
` Re: increased max_parallel_workers_per_gather results in fewer workers?
2020-06-04 08:56 UTC Tomas Vondra <tomas.vondra@2ndquadrant.com>
` Re: increased max_parallel_workers_per_gather results in fewer workers?
2020-06-04 09:30 UTC Magnus Hagander <magnus@hagander.net>
` Re: increased max_parallel_workers_per_gather results in fewer workers?
2020-06-04 16:41 UTC Philip Semanchuk <philip@americanefficient.com>
` Re: increased max_parallel_workers_per_gather results in fewer workers?
2020-06-04 17:45 UTC Sebastian Dressler <sebastian@swarm64.com>
` Re: increased max_parallel_workers_per_gather results in fewer workers?
2020-06-04 18:37 UTC Philip Semanchuk <philip@americanefficient.com>
` Re: increased max_parallel_workers_per_gather results in fewer workers?
2020-06-04 19:03 UTC Sebastian Dressler <sebastian@swarm64.com>
` Re: increased max_parallel_workers_per_gather results in fewer workers?
2020-06-04 21:29 UTC Philip Semanchuk <philip@americanefficient.com>
[13+ messages in thread]
Configuration
2020-06-01 12:09 UTC sugnathi hai <suganhai@yahoo.com>
` Re: Configuration
2020-06-01 13:24 UTC Filip Rembiałkowski <plk.zuber@gmail.com>
[2+ messages in thread]
Performance tunning
2020-05-30 07:36 UTC sugnathi hai <suganhai@yahoo.com>
` Re: Performance tunning
2020-05-30 07:43 UTC Pavel Stehule <pavel.stehule@gmail.com>
` Re: Performance tunning
2020-05-30 14:19 UTC Justin Pryzby <pryzby@telsasoft.com>
` Re: Performance tunning
2020-05-30 14:55 UTC Jeff Janes <jeff.janes@gmail.com>
[4+ messages in thread]
PostgreSQL performance problem moving from 9.6.17 to 12.3
2020-05-28 15:56 UTC Kenneth Marshall <ktm@rice.edu>
` Re: PostgreSQL performance problem moving from 9.6.17 to 12.3
2020-05-28 16:42 UTC Tom Lane <tgl@sss.pgh.pa.us>
[2+ messages in thread]
Strategy for materialisation and centralisation of data
2020-05-22 14:48 UTC Rory Campbell-Lange <rory@campbell-lange.net>
Suggestion to improve query performance of data validation in proc.
2020-05-22 06:41 UTC postgann2020 s <postgann2020@gmail.com>
` Suggestion to improve query performance for GIS query.
2020-05-22 06:59 UTC postgann2020 s <postgann2020@gmail.com>
` Re: Suggestion to improve query performance of data validation in proc.
2020-05-22 07:06 UTC David G. Johnston <david.g.johnston@gmail.com>
` Re: Suggestion to improve query performance for GIS query.
2020-05-22 07:14 UTC David G. Johnston <david.g.johnston@gmail.com>
` Re: Suggestion to improve query performance for GIS query.
2020-05-22 07:16 UTC Mohammed Afsar <vmdapsar@gmail.com>
` Re: Suggestion to improve query performance for GIS query.
2020-05-22 07:34 UTC postgann2020 s <postgann2020@gmail.com>
` Re: Suggestion to improve query performance of data validation in proc.
2020-05-22 07:44 UTC postgann2020 s <postgann2020@gmail.com>
` Re: Suggestion to improve query performance of data validation in proc.
2020-05-22 08:09 UTC David G. Johnston <david.g.johnston@gmail.com>
` Re: Suggestion to improve query performance of data validation in proc.
2020-05-22 14:26 UTC Michael Lewis <mlewis@entrata.com>
[9+ messages in thread]
Request to help on GIS Query improvement suggestion.
2020-05-22 10:53 UTC postggen2020 s <postggen2020@gmail.com>
` Re: Request to help on GIS Query improvement suggestion.
2020-05-22 14:14 UTC Michael Lewis <mlewis@entrata.com>
[2+ messages in thread]
Suggestion on index creation for TEXT data field
2020-05-21 14:27 UTC postgann2020 s <postgann2020@gmail.com>
` Re: Suggestion on index creation for TEXT data field
2020-05-21 14:36 UTC David G. Johnston <david.g.johnston@gmail.com>
` Re: Suggestion on index creation for TEXT data field
2020-05-21 14:44 UTC postgann2020 s <postgann2020@gmail.com>
` Re: Suggestion on index creation for TEXT data field
2020-05-21 14:45 UTC Adrian Klaver <adrian.klaver@aklaver.com>
` Re: Suggestion on index creation for TEXT data field
2020-05-21 14:51 UTC David G. Johnston <david.g.johnston@gmail.com>
` Re: Suggestion on index creation for TEXT data field
2020-05-21 14:53 UTC postgann2020 s <postgann2020@gmail.com>
[6+ messages in thread]
Suggestion on table analyze
2020-05-21 14:18 UTC postgann2020 s <postgann2020@gmail.com>
` Re: Suggestion on table analyze
2020-05-21 14:41 UTC Adrian Klaver <adrian.klaver@aklaver.com>
` Re: Suggestion on table analyze
2020-05-21 14:48 UTC postgann2020 s <postgann2020@gmail.com>
[3+ messages in thread]
Suggestion to improve query performance.
2020-05-20 18:20 UTC postgann2020 s <postgann2020@gmail.com>
OOM Killer kills PostgreSQL
2020-05-20 07:30 UTC Piotr Włodarczyk <piotrwlodarczyk89@gmail.com>
` Re: OOM Killer kills PostgreSQL
2020-05-20 08:22 UTC Laurenz Albe <laurenz.albe@cybertec.at>
` Re: OOM Killer kills PostgreSQL
2020-05-20 08:28 UTC Piotr Włodarczyk <piotrwlodarczyk89@gmail.com>
` Re: OOM Killer kills PostgreSQL
2020-05-20 08:40 UTC Fabio Pardi <f.pardi@portavita.eu>
` Re: OOM Killer kills PostgreSQL
2020-05-20 08:46 UTC Justin Pryzby <pryzby@telsasoft.com>
` Re: OOM Killer kills PostgreSQL
2020-05-20 16:54 UTC Stephen Frost <sfrost@snowman.net>
[6+ messages in thread]
Execution time from >1s -> 80m+ when extra columns added in SELECT for sub-query
2020-05-18 18:42 UTC A Guy Named Ryan <aguynamedryan@gmail.com>
` Re: Execution time from >1s -> 80m+ when extra columns added in SELECT for sub-query
2020-05-18 19:17 UTC Pavel Stehule <pavel.stehule@gmail.com>
` Re: Execution time from >1s -> 80m+ when extra columns added in SELECT for sub-query
2020-05-18 20:49 UTC A Guy Named Ryan <aguynamedryan@gmail.com>
` Re: Execution time from >1s -> 80m+ when extra columns added in SELECT for sub-query
2020-05-18 21:58 UTC Tom Lane <tgl@sss.pgh.pa.us>
[4+ messages in thread]
Plan not skipping unnecessary inner join
2020-05-14 05:44 UTC Matthew Nelson <postgres@binarykeep.com>
` Re: Plan not skipping unnecessary inner join
2020-05-14 06:45 UTC David Wheeler <hippysoyboy@gmail.com>
` Re: Plan not skipping unnecessary inner join
2020-05-15 17:36 UTC Matthew Nelson <postgres@binarykeep.com>
` Re: Plan not skipping unnecessary inner join
2020-05-17 12:32 UTC Ranier Vilela <ranier.vf@gmail.com>
` Re: Plan not skipping unnecessary inner join
2020-05-17 13:31 UTC Justin Pryzby <pryzby@telsasoft.com>
` Re: Plan not skipping unnecessary inner join
2020-05-17 14:05 UTC Ranier Vilela <ranier.vf@gmail.com>
[6+ messages in thread]
Please help! Query jumps from 1s -> 4m
2020-05-03 08:58 UTC James Thompson <james@jthompson.dev>
` Re: Please help! Query jumps from 1s -> 4m
2020-05-03 15:38 UTC Justin Pryzby <pryzby@telsasoft.com>
` Re: Please help! Query jumps from 1s -> 4m
2020-05-04 19:12 UTC Justin Pryzby <pryzby@telsasoft.com>
` Re: Please help! Query jumps from 1s -> 4m
2020-05-04 19:12 UTC James Thompson <james@jthompson.dev>
` Re: Please help! Query jumps from 1s -> 4m
2020-05-04 20:12 UTC David Rowley <dgrowleyml@gmail.com>
` Re: Please help! Query jumps from 1s -> 4m
2020-05-05 08:08 UTC Laurenz Albe <laurenz.albe@cybertec.at>
` Re: Please help! Query jumps from 1s -> 4m
2020-05-05 19:28 UTC Justin Pryzby <pryzby@telsasoft.com>
` Re: Please help! Query jumps from 1s -> 4m
2020-05-05 21:10 UTC James Thompson <james@jthompson.dev>
` Re: Please help! Query jumps from 1s -> 4m
2020-05-05 21:35 UTC Justin Pryzby <pryzby@telsasoft.com>
` Re: Please help! Query jumps from 1s -> 4m
2020-05-05 21:42 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: Please help! Query jumps from 1s -> 4m
2020-05-13 14:17 UTC James Thompson <james@jthompson.dev>
[11+ messages in thread]
Inaccurate Rows estimate for "Bitmap And" causes Planner to choose wrong join
2020-05-06 16:19 UTC Steve Pritchard <steve.pritchard@bto.org>
` Re: Inaccurate Rows estimate for "Bitmap And" causes Planner to choose wrong join
2020-05-06 16:34 UTC Justin Pryzby <pryzby@telsasoft.com>
` Re: Inaccurate Rows estimate for "Bitmap And" causes Planner to choose wrong join
2020-05-06 18:24 UTC Jeff Janes <jeff.janes@gmail.com>
` Re: Inaccurate Rows estimate for "Bitmap And" causes Planner to choose wrong join
2020-05-13 09:33 UTC Steve Pritchard <steve.pritchard@bto.org>
[4+ messages in thread]
AutoVacuum and growing transaction XID's
2020-05-07 18:23 UTC github kran <githubkran@gmail.com>
` Re: AutoVacuum and growing transaction XID's
2020-05-07 18:32 UTC Michael Lewis <mlewis@entrata.com>
` Re: AutoVacuum and growing transaction XID's
2020-05-07 21:18 UTC github kran <githubkran@gmail.com>
` Re: AutoVacuum and growing transaction XID's
2020-05-08 01:51 UTC github kran <githubkran@gmail.com>
` Re: AutoVacuum and growing transaction XID's
2020-05-08 04:01 UTC David Rowley <dgrowleyml@gmail.com>
` Re: AutoVacuum and growing transaction XID's
2020-05-08 04:04 UTC David Rowley <dgrowleyml@gmail.com>
` Re: AutoVacuum and growing transaction XID's
2020-05-08 06:06 UTC github kran <githubkran@gmail.com>
` Re: AutoVacuum and growing transaction XID's
2020-05-08 06:17 UTC github kran <githubkran@gmail.com>
` Re: AutoVacuum and growing transaction XID's
2020-05-08 21:11 UTC Michael Lewis <mlewis@entrata.com>
` Re: AutoVacuum and growing transaction XID's
2020-05-12 15:40 UTC github kran <githubkran@gmail.com>
[10+ messages in thread]
600 million rows of data. Bad hardware or need partitioning?
2020-05-04 03:27 UTC Arya F <arya6000@gmail.com>
` Re: 600 million rows of data. Bad hardware or need partitioning?
2020-05-04 03:45 UTC Michael Lewis <mlewis@entrata.com>
` Re: 600 million rows of data. Bad hardware or need partitioning?
2020-05-04 03:51 UTC Arya F <arya6000@gmail.com>
` Re: 600 million rows of data. Bad hardware or need partitioning?
2020-05-04 04:44 UTC David Rowley <dgrowleyml@gmail.com>
` Re: 600 million rows of data. Bad hardware or need partitioning?
2020-05-04 09:21 UTC Justin Pryzby <pryzby@telsasoft.com>
` Re: 600 million rows of data. Bad hardware or need partitioning?
2020-05-06 00:15 UTC Arya F <arya6000@gmail.com>
` Re: 600 million rows of data. Bad hardware or need partitioning?
2020-05-06 00:31 UTC Arya F <arya6000@gmail.com>
` Re: 600 million rows of data. Bad hardware or need partitioning?
2020-05-06 01:37 UTC Justin Pryzby <pryzby@telsasoft.com>
` Re: 600 million rows of data. Bad hardware or need partitioning?
2020-05-10 04:10 UTC Arya F <arya6000@gmail.com>
[9+ messages in thread]
pg_attribute, pg_class, pg_depend grow huge in count and size with multiple tenants.
2020-05-07 17:10 UTC samhitha g <samhithagarudadri@gmail.com>
` Re: pg_attribute, pg_class, pg_depend grow huge in count and size with multiple tenants.
2020-05-07 20:17 UTC David G. Johnston <david.g.johnston@gmail.com>
` Re: pg_attribute, pg_class, pg_depend grow huge in count and size with multiple tenants.
2020-05-07 20:28 UTC Avinash Kumar <avinash.vallarapu@gmail.com>
` Re: pg_attribute, pg_class, pg_depend grow huge in count and size with multiple tenants.
2020-05-07 21:08 UTC Rory Campbell-Lange <rory@campbell-lange.net>
` Re: pg_attribute, pg_class, pg_depend grow huge in count and size with multiple tenants.
2020-05-07 21:17 UTC Avinash Kumar <avinash.vallarapu@gmail.com>
` Re: pg_attribute, pg_class, pg_depend grow huge in count and size with multiple tenants.
2020-05-08 06:31 UTC Laurenz Albe <laurenz.albe@cybertec.at>
` Re: pg_attribute, pg_class, pg_depend grow huge in count and size with multiple tenants.
2020-05-08 06:47 UTC Avinash Kumar <avinash.vallarapu@gmail.com>
` Re: pg_attribute, pg_class, pg_depend grow huge in count and size with multiple tenants.
2020-05-08 06:53 UTC Laurenz Albe <laurenz.albe@cybertec.at>
` Re: pg_attribute, pg_class, pg_depend grow huge in count and size with multiple tenants.
2020-05-08 10:14 UTC Avinash Kumar <avinash.vallarapu@gmail.com>
` Re: pg_attribute, pg_class, pg_depend grow huge in count and size with multiple tenants.
2020-05-08 13:01 UTC MichaelDBA <MichaelDBA@sqlexec.com>
` Re: pg_attribute, pg_class, pg_depend grow huge in count and size with multiple tenants.
2020-05-08 13:44 UTC Jeff Janes <jeff.janes@gmail.com>
` Re: pg_attribute, pg_class, pg_depend grow huge in count and size with multiple tenants.
2020-05-08 13:54 UTC Jeff Janes <jeff.janes@gmail.com>
[12+ messages in thread]
Explain plan changes - IN CLAUSE ( Passing direct values Vs INNER Query )
2020-05-07 11:19 UTC Amarendra Konda <amar.vijaya@gmail.com>
` Re: Explain plan changes - IN CLAUSE ( Passing direct values Vs INNER Query )
2020-05-07 14:40 UTC Adrian Klaver <adrian.klaver@aklaver.com>
` Re: Explain plan changes - IN CLAUSE ( Passing direct values Vs INNER Query )
2020-05-07 15:46 UTC David G. Johnston <david.g.johnston@gmail.com>
` Re: Explain plan changes - IN CLAUSE ( Passing direct values Vs INNER Query )
2020-05-07 17:36 UTC Amarendra Konda <amar.vijaya@gmail.com>
` Re: Explain plan changes - IN CLAUSE ( Passing direct values Vs INNER Query )
2020-05-07 17:49 UTC Amarendra Konda <amar.vijaya@gmail.com>
` Re: Explain plan changes - IN CLAUSE ( Passing direct values Vs INNER Query )
2020-05-07 18:07 UTC Amarendra Konda <amar.vijaya@gmail.com>
` Re: Explain plan changes - IN CLAUSE ( Passing direct values Vs INNER Query )
2020-05-07 18:51 UTC Amarendra Konda <amar.vijaya@gmail.com>
` Re: Explain plan changes - IN CLAUSE ( Passing direct values Vs INNER Query )
2020-05-07 19:25 UTC Adrian Klaver <adrian.klaver@aklaver.com>
` Re: Explain plan changes - IN CLAUSE ( Passing direct values Vs INNER Query )
2020-05-07 19:30 UTC Virendra Kumar <viru_7683@yahoo.com>
` Re: Explain plan changes - IN CLAUSE ( Passing direct values Vs INNER Query )
2020-05-07 21:21 UTC David G. Johnston <david.g.johnston@gmail.com>
` Re: Explain plan changes - IN CLAUSE ( Passing direct values Vs INNER Query )
2020-05-07 21:26 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: Explain plan changes - IN CLAUSE ( Passing direct values Vs INNER Query )
2020-05-07 21:59 UTC David G. Johnston <david.g.johnston@gmail.com>
` Re: Explain plan changes - IN CLAUSE ( Passing direct values Vs INNER Query )
2020-05-07 23:46 UTC David Rowley <dgrowleyml@gmail.com>
[13+ messages in thread]
NUMA settings
2020-04-29 06:54 UTC Marc Rechté <marc4@rechte.fr>
` Re: NUMA settings
2020-04-29 08:50 UTC Laurenz Albe <laurenz.albe@cybertec.at>
` Re: NUMA settings
2020-05-04 16:20 UTC Andres Freund <andres@anarazel.de>
` Re: NUMA settings
2020-05-05 05:56 UTC Marc Rechté <marc4@rechte.fr>
` Re: NUMA settings
2020-05-05 08:00 UTC Laurenz Albe <laurenz.albe@cybertec.at>
` Re: NUMA settings
2020-05-05 08:11 UTC Marc Rechté <marc4@rechte.fr>
` Re: NUMA settings
2020-05-05 08:25 UTC Laurenz Albe <laurenz.albe@cybertec.at>
[7+ messages in thread]
good book or any other resources for Postgresql
2020-05-04 22:45 UTC Bhupendra Babu <bbabu12@gmail.com>
` Re: good book or any other resources for Postgresql
2020-05-04 23:41 UTC Michael Lewis <mlewis@entrata.com>
` Re: good book or any other resources for Postgresql
2020-05-04 23:45 UTC Craig Jackson <craig.jackson@broadcom.com>
` Re: good book or any other resources for Postgresql
2020-05-05 03:37 UTC Bhupendra Babu <bbabu12@gmail.com>
[4+ messages in thread]
Duplicate WHERE condition changes performance and plan
2020-04-15 19:55 UTC singh400@gmail.com <singh400@gmail.com>
` Re: Duplicate WHERE condition changes performance and plan
2020-04-15 23:57 UTC David Rowley <dgrowleyml@gmail.com>
` Re: Duplicate WHERE condition changes performance and plan
2020-04-20 00:50 UTC singh400@gmail.com <singh400@gmail.com>
` Re: Duplicate WHERE condition changes performance and plan
2020-04-20 02:33 UTC Justin Pryzby <pryzby@telsasoft.com>
` Re: Duplicate WHERE condition changes performance and plan
2020-04-24 16:33 UTC singh400@gmail.com <singh400@gmail.com>
` Re: Duplicate WHERE condition changes performance and plan
2020-05-03 11:39 UTC singh400@gmail.com <singh400@gmail.com>
` Re: Duplicate WHERE condition changes performance and plan
2020-05-04 17:11 UTC Michael Lewis <mlewis@entrata.com>
[7+ messages in thread]
Recursive query slow on strange conditions
2020-04-27 17:49 UTC Jean-Christophe Boggio <postgresql@thefreecat.org>
` Re: Recursive query slow on strange conditions
2020-04-27 18:10 UTC Justin Pryzby <pryzby@telsasoft.com>
` Re: Recursive query slow on strange conditions
2020-04-27 19:37 UTC Andreas Joseph Krogh <andreas@visena.com>
` Re: Recursive query slow on strange conditions
2020-04-27 20:22 UTC Jean-Christophe Boggio <postgresql@thefreecat.org>
` Re: Recursive query slow on strange conditions
2020-05-04 16:12 UTC Jean-Christophe Boggio <postgresql@thefreecat.org>
` Re: Recursive query slow on strange conditions
2020-05-04 16:20 UTC David G. Johnston <david.g.johnston@gmail.com>
` Re: Recursive query slow on strange conditions
2020-05-04 16:25 UTC Jean-Christophe Boggio <postgresql@thefreecat.org>
[7+ messages in thread]
Best partition type for billions of addresses
2020-05-02 13:20 UTC Arya F <arya6000@gmail.com>
` Re: Best partition type for billions of addresses
2020-05-02 14:00 UTC Justin Pryzby <pryzby@telsasoft.com>
` Re: Best partition type for billions of addresses
2020-05-02 14:01 UTC Stephen Frost <sfrost@snowman.net>
` Re: Best partition type for billions of addresses
2020-05-02 14:33 UTC Arya F <arya6000@gmail.com>
` Re: Best partition type for billions of addresses
2020-05-02 14:39 UTC Stephen Frost <sfrost@snowman.net>
[5+ messages in thread]
The query plan get all columns but I'm using only one column.
2020-04-24 21:11 UTC Moises Lopez <moylop260@vauxoo.com>
` Re: The query plan get all columns but I'm using only one column.
2020-04-25 14:24 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: The query plan get all columns but I'm using only one column.
2020-04-25 20:40 UTC Michael Lewis <mlewis@entrata.com>
` Re: The query plan get all columns but I'm using only one column.
2020-04-29 19:21 UTC Moises Lopez <moylop260@vauxoo.com>
` Re: The query plan get all columns but I'm using only one column.
2020-04-29 19:36 UTC Michael Lewis <mlewis@entrata.com>
` Re: The query plan get all columns but I'm using only one column.
2020-04-30 15:52 UTC Michael Lewis <mlewis@entrata.com>
` Re: The query plan get all columns but I'm using only one column.
2020-04-30 16:26 UTC Moises Lopez <moylop260@vauxoo.com>
[7+ 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