pg.ddx.io pgsql-performance@postgresql.org mailing list archive
help / color / mirror / Atom feedDB connection issue suggestions
2022-05-10 16:59 UTC Sudhir Guna <sudhir.guna.sg@gmail.com>
` Re: DB connection issue suggestions
2022-05-10 18:13 UTC MichaelDBA Vitale <michaeldba@sqlexec.com>
` Re: DB connection issue suggestions
2022-05-10 18:15 UTC Justin Pryzby <pryzby@telsasoft.com>
` Re: DB connection issue suggestions
2022-05-10 18:54 UTC Ranier Vilela <ranier.vf@gmail.com>
` Re: DB connection issue suggestions
2022-05-11 01:44 UTC Sudhir Guna <sudhir.guna.sg@gmail.com>
` Re: DB connection issue suggestions
2022-05-11 01:46 UTC Sudhir Guna <sudhir.guna.sg@gmail.com>
` Re: DB connection issue suggestions
2022-05-11 01:52 UTC Sudhir Guna <sudhir.guna.sg@gmail.com>
` Re: DB connection issue suggestions
2022-05-11 06:13 UTC Laurenz Albe <laurenz.albe@cybertec.at>
` Re: DB connection issue suggestions
2022-05-11 06:30 UTC Anbazhagan M <anbazhagan.m@instaclustr.com>
` Re: DB connection issue suggestions
2022-05-11 07:11 UTC Sudhir Guna <sudhir.guna.sg@gmail.com>
` Re: DB connection issue suggestions
2022-05-11 11:45 UTC Ranier Vilela <ranier.vf@gmail.com>
` Re: DB connection issue suggestions
2022-05-11 19:09 UTC Justin Pryzby <pryzby@telsasoft.com>
` Re: DB connection issue suggestions
2022-05-12 04:53 UTC Sudhir Guna <sudhir.guna.sg@gmail.com>
` Re: DB connection issue suggestions
2022-05-13 04:08 UTC Justin Pryzby <pryzby@telsasoft.com>
[14+ messages in thread]
Why is there a Sort after an Index Only Scan?
2022-05-04 23:15 UTC André Hänsel <andre@webkr.de>
` Re: Why is there a Sort after an Index Only Scan?
2022-05-04 23:37 UTC Jeff Janes <jeff.janes@gmail.com>
` Re: Why is there a Sort after an Index Only Scan?
2022-05-04 23:42 UTC David Rowley <dgrowleyml@gmail.com>
` RE: Why is there a Sort after an Index Only Scan?
2022-05-05 01:12 UTC André Hänsel <andre@webkr.de>
` Re: Why is there a Sort after an Index Only Scan?
2022-05-05 02:08 UTC Tom Lane <tgl@sss.pgh.pa.us>
[5+ messages in thread]
Window partial fetch optimization
2022-05-03 18:11 UTC Levi Aul <levi@leviaul.com>
` Re: Window partial fetch optimization
2022-05-03 22:12 UTC David Rowley <dgrowleyml@gmail.com>
` Re: Window partial fetch optimization
2022-05-04 21:56 UTC Jeff Janes <jeff.janes@gmail.com>
[3+ messages in thread]
Useless memoize path generated for unique join on primary keys
2022-05-03 11:05 UTC Benjamin Coutu <ben.coutu@zeyos.com>
` Re: Useless memoize path generated for unique join on primary keys
2022-05-03 11:43 UTC David Rowley <dgrowleyml@gmail.com>
` Re: Useless memoize path generated for unique join on primary keys
2022-05-03 12:21 UTC Benjamin Coutu <ben.coutu@zeyos.com>
` Re: Useless memoize path generated for unique join on primary keys
2022-05-03 12:31 UTC David Rowley <dgrowleyml@gmail.com>
[4+ messages in thread]
FATAL: canceling authentication due to timeout
2022-04-29 10:59 UTC aditya desai <admad123@gmail.com>
` Fwd: FATAL: canceling authentication due to timeout
2022-04-29 11:23 UTC aditya desai <admad123@gmail.com>
[2+ messages in thread]
LISTEN NOTIFY sometimes huge delay
2022-04-28 14:28 UTC Peter Eser HEUFT [Germany] <peter.eser@heuft.com>
` Re: LISTEN NOTIFY sometimes huge delay
2022-04-28 16:38 UTC Tom Lane <tgl@sss.pgh.pa.us>
[2+ messages in thread]
Performance differential when 0 values present vs when 1 values present. Planner return 52k rows when 0 expected.
2022-04-22 14:53 UTC Emil Iggland <emil.iggland@metrima.com>
` Re: Performance differential when 0 values present vs when 1 values present. Planner return 52k rows when 0 expected.
2022-04-25 16:00 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: Performance differential when 0 values present vs when 1 values present. Planner return 52k rows when 0 expected.
2022-04-26 07:41 UTC Emil Iggland <emil.iggland@metrima.com>
` Re: Performance differential when 0 values present vs when 1 values present. Planner return 52k rows when 0 expected.
2022-04-27 08:22 UTC David Rowley <dgrowleyml@gmail.com>
` Re: Performance differential when 0 values present vs when 1 values present. Planner return 52k rows when 0 expected.
2022-04-28 08:09 UTC Emil Iggland <emil.iggland@metrima.com>
[5+ messages in thread]
Unworkable plan above certain row count
2022-04-28 00:52 UTC André Hänsel <andre@webkr.de>
` Re: Unworkable plan above certain row count
2022-04-28 02:08 UTC Tom Lane <tgl@sss.pgh.pa.us>
[2+ messages in thread]
Query Planner not taking advantage of HASH PARTITION
2022-04-14 23:36 UTC Benjamin Tingle <ben@tingle.org>
` Re: Query Planner not taking advantage of HASH PARTITION
2022-04-17 16:09 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: Query Planner not taking advantage of HASH PARTITION
2022-04-17 17:07 UTC Benjamin Tingle <ben@tingle.org>
` Re: Query Planner not taking advantage of HASH PARTITION
2022-04-17 18:20 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: Query Planner not taking advantage of HASH PARTITION
2022-04-17 18:50 UTC Alvaro Herrera <alvherre@alvh.no-ip.org>
` Re: Query Planner not taking advantage of HASH PARTITION
2022-04-21 02:11 UTC Benjamin Tingle <ben@tingle.org>
` Re: Query Planner not taking advantage of HASH PARTITION
2022-04-21 11:52 UTC Justin Pryzby <pryzby@telsasoft.com>
[7+ messages in thread]
Postgresql TPS Bottleneck
2022-03-31 11:50 UTC wakandavision@outlook.com
` Re: Postgresql TPS Bottleneck
2022-03-31 14:18 UTC Guillaume Cottenceau <gc@mnc.ch>
` Re: Postgresql TPS Bottleneck
2022-03-31 18:55 UTC MichaelDBA <MichaelDBA@sqlexec.com>
` Re: Postgresql TPS Bottleneck
2022-03-31 19:16 UTC Tomas Vondra <tomas.vondra@enterprisedb.com>
` Re: Postgresql TPS Bottleneck
2022-04-01 02:40 UTC Mladen Gogala <gogala.mladen@gmail.com>
` Re: Postgresql TPS Bottleneck
2022-04-20 06:49 UTC wakandavision@outlook.com
` Re: Postgresql TPS Bottleneck
2022-04-20 15:49 UTC Jeff Janes <jeff.janes@gmail.com>
` Re: Postgresql TPS Bottleneck
2022-04-20 16:35 UTC wakandavision@outlook.com
` Re: Postgresql TPS Bottleneck
2022-04-20 18:18 UTC Benedict Holland <benedict.m.holland@gmail.com>
[9+ messages in thread]
significant jump in sql statement timing for on server vs a remote connection
2022-04-19 21:00 UTC Sbob <sbob@quadratum-braccas.com>
` Re: significant jump in sql statement timing for on server vs a remote connection
2022-04-19 21:04 UTC Justin Pryzby <pryzby@telsasoft.com>
` Re: significant jump in sql statement timing for on server vs a remote connection
2022-04-20 04:17 UTC Jeff Janes <jeff.janes@gmail.com>
` Re: significant jump in sql statement timing for on server vs a remote connection
2022-04-20 15:16 UTC Sbob <sbob@quadratum-braccas.com>
` Re: significant jump in sql statement timing for on server vs a remote connection
2022-04-20 15:51 UTC Ranier Vilela <ranier.vf@gmail.com>
[5+ messages in thread]
How to find all SQLs executed by a transaction id?
2022-04-19 12:35 UTC Patil, Ravi <Ravi.Patil@FMR.com>
How to find the final transformed query in postgresql
2022-04-18 14:02 UTC Goti <aryan.goti@gmail.com>
` Re: How to find the final transformed query in postgresql
2022-04-18 14:13 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: How to find the final transformed query in postgresql
2022-04-18 14:31 UTC Goti <aryan.goti@gmail.com>
[3+ messages in thread]
Query Tunning related to function
2022-04-14 06:03 UTC Kumar, Mukesh <MKumar@peabodyenergy.com>
` Re: Query Tunning related to function
2022-04-14 14:26 UTC Ranier Vilela <ranier.vf@gmail.com>
` RE: Query Tunning related to function
2022-04-14 14:44 UTC Kumar, Mukesh <MKumar@peabodyenergy.com>
` RE: Query Tunning related to function
2022-04-14 18:14 UTC Michel SALAIS <msalais@msym.fr>
` RE: Query Tunning related to function
2022-04-14 18:45 UTC Kumar, Mukesh <MKumar@peabodyenergy.com>
` Re: Query Tunning related to function
2022-04-14 22:13 UTC Bhupendra Babu <bbabu12@gmail.com>
` RE: Query Tunning related to function
2022-04-15 06:13 UTC Kumar, Mukesh <MKumar@peabodyenergy.com>
` RE: Query Tunning related to function
2022-04-15 16:46 UTC Kumar, Mukesh <MKumar@peabodyenergy.com>
` Re: Query Tunning related to function
2022-04-17 03:13 UTC Justin Pryzby <pryzby@telsasoft.com>
` Re: Query Tunning related to function
2022-04-17 16:47 UTC David G. Johnston <david.g.johnston@gmail.com>
[10+ messages in thread]
Performance for SQL queries on Azure PostgreSQL PaaS instance
2022-04-12 09:10 UTC Kumar, Mukesh <MKumar@peabodyenergy.com>
` Re: Performance for SQL queries on Azure PostgreSQL PaaS instance
2022-04-12 14:23 UTC Frits Jalvingh <jal@etc.to>
` Re: Performance for SQL queries on Azure PostgreSQL PaaS instance
2022-04-12 15:06 UTC Tomas Vondra <tomas.vondra@enterprisedb.com>
` Re: Performance for SQL queries on Azure PostgreSQL PaaS instance
2022-04-13 08:34 UTC Laurenz Albe <laurenz.albe@cybertec.at>
` RE: Performance for SQL queries on Azure PostgreSQL PaaS instance
2022-04-13 08:42 UTC Kumar, Mukesh <MKumar@peabodyenergy.com>
` Re: Performance for SQL queries on Azure PostgreSQL PaaS instance
2022-04-13 11:17 UTC andrew cooke <andrew@acooke.org>
` Re: Performance for SQL queries on Azure PostgreSQL PaaS instance
2022-04-14 20:20 UTC overland <overland@recarea.com>
[7+ messages in thread]
SQL performance issue after migration from Oracle to Aurora postgres
2022-04-14 09:35 UTC Goti <aryan.goti@gmail.com>
` Re: SQL performance issue after migration from Oracle to Aurora postgres
2022-04-14 14:40 UTC Andrew Dunstan <andrew@dunslane.net>
[2+ messages in thread]
An I/O error occurred while sending to the backend (PG 13.4)
2021-12-04 17:32 UTC ldh@laurent-hasson.com <ldh@laurent-hasson.com>
` Re: An I/O error occurred while sending to the backend (PG 13.4)
2021-12-04 17:59 UTC Justin Pryzby <pryzby@telsasoft.com>
` RE: An I/O error occurred while sending to the backend (PG 13.4)
2021-12-04 19:18 UTC ldh@laurent-hasson.com <ldh@laurent-hasson.com>
` Re: An I/O error occurred while sending to the backend (PG 13.4)
2021-12-04 19:53 UTC Justin Pryzby <pryzby@telsasoft.com>
` RE: An I/O error occurred while sending to the backend (PG 13.4)
2022-02-24 00:47 UTC ldh@laurent-hasson.com <ldh@laurent-hasson.com>
` Re: An I/O error occurred while sending to the backend (PG 13.4)
2022-02-24 01:04 UTC Justin Pryzby <pryzby@telsasoft.com>
` Re: An I/O error occurred while sending to the backend (PG 13.4)
2022-02-24 02:00 UTC Justin Pryzby <pryzby@telsasoft.com>
` Re: An I/O error occurred while sending to the backend (PG 13.4)
2022-02-24 11:50 UTC Ranier Vilela <ranier.vf@gmail.com>
` Re: An I/O error occurred while sending to the backend (PG 13.4)
2022-02-24 12:59 UTC Justin Pryzby <pryzby@telsasoft.com>
` Re: An I/O error occurred while sending to the backend (PG 13.4)
2022-02-24 13:46 UTC Ranier Vilela <ranier.vf@gmail.com>
` Re: An I/O error occurred while sending to the backend (PG 13.4)
2022-02-25 13:02 UTC Justin Pryzby <pryzby@telsasoft.com>
` RE: An I/O error occurred while sending to the backend (PG 13.4)
2022-02-28 16:50 UTC ldh@laurent-hasson.com <ldh@laurent-hasson.com>
` RE: An I/O error occurred while sending to the backend (PG 13.4)
2022-02-28 21:43 UTC ldh@laurent-hasson.com <ldh@laurent-hasson.com>
` Re: An I/O error occurred while sending to the backend (PG 13.4)
2022-02-28 22:05 UTC Justin Pryzby <pryzby@telsasoft.com>
` RE: An I/O error occurred while sending to the backend (PG 13.4)
2022-03-01 16:28 UTC ldh@laurent-hasson.com <ldh@laurent-hasson.com>
` Re: An I/O error occurred while sending to the backend (PG 13.4)
2022-03-01 19:26 UTC Justin Pryzby <pryzby@telsasoft.com>
` Re: An I/O error occurred while sending to the backend (PG 13.4)
2022-03-02 01:15 UTC Ranier Vilela <ranier.vf@gmail.com>
` RE: An I/O error occurred while sending to the backend (PG 13.4)
2022-03-03 14:55 UTC ldh@laurent-hasson.com <ldh@laurent-hasson.com>
` Re: An I/O error occurred while sending to the backend (PG 13.4)
2022-03-03 16:33 UTC Ranier Vilela <ranier.vf@gmail.com>
` Re: An I/O error occurred while sending to the backend (PG 13.4)
2022-03-03 16:46 UTC Justin Pryzby <pryzby@telsasoft.com>
` Re: An I/O error occurred while sending to the backend (PG 13.4)
2022-03-03 16:56 UTC Ranier Vilela <ranier.vf@gmail.com>
` RE: An I/O error occurred while sending to the backend (PG 13.4)
2022-03-03 18:19 UTC ldh@laurent-hasson.com <ldh@laurent-hasson.com>
` Re: An I/O error occurred while sending to the backend (PG 13.4)
2022-03-03 18:22 UTC Ranier Vilela <ranier.vf@gmail.com>
` RE: An I/O error occurred while sending to the backend (PG 13.4)
2022-04-13 15:36 UTC ldh@laurent-hasson.com <ldh@laurent-hasson.com>
` Re: An I/O error occurred while sending to the backend (PG 13.4)
2022-04-13 15:43 UTC Justin Pryzby <pryzby@telsasoft.com>
[25+ messages in thread]
Slow Planning Times
2022-04-07 00:26 UTC Saurabh Sehgal <saurabh.r.s@gmail.com>
` Re: Slow Planning Times
2022-04-07 00:40 UTC Saurabh Sehgal <saurabh.r.s@gmail.com>
` Re: Slow Planning Times
2022-04-07 00:54 UTC David G. Johnston <david.g.johnston@gmail.com>
` Re: Slow Planning Times
2022-04-07 01:47 UTC Saurabh Sehgal <saurabh.r.s@gmail.com>
` Re: Slow Planning Times
2022-04-07 02:57 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: Slow Planning Times
2022-04-07 04:09 UTC Saurabh Sehgal <saurabh.r.s@gmail.com>
[6+ messages in thread]
HIGH IO and Less CPU utilization
2022-03-29 18:04 UTC Rambabu g <rambabu.g2564@gmail.com>
` Re: HIGH IO and Less CPU utilization
2022-03-29 18:24 UTC Justin Pryzby <pryzby@telsasoft.com>
` Re: HIGH IO and Less CPU utilization
2022-03-29 19:22 UTC Rambabu g <rambabu.g2564@gmail.com>
` Re: HIGH IO and Less CPU utilization
2022-03-29 19:39 UTC Justin Pryzby <pryzby@telsasoft.com>
` Re: HIGH IO and Less CPU utilization
2022-03-30 04:47 UTC Rambabu g <rambabu.g2564@gmail.com>
` Re: HIGH IO and Less CPU utilization
2022-03-31 06:49 UTC Justin Pryzby <pryzby@telsasoft.com>
` Re: HIGH IO and Less CPU utilization
2022-03-31 14:44 UTC Mladen Gogala <gogala.mladen@gmail.com>
` Re: HIGH IO and Less CPU utilization
2022-04-04 07:47 UTC Rambabu g <rambabu.g2564@gmail.com>
[8+ messages in thread]
High process memory consumption when running sort
2022-03-23 14:42 UTC Shai Shapira <Shai.Shapira@Amdocs.com>
` Re: High process memory consumption when running sort
2022-03-23 15:20 UTC Justin Pryzby <pryzby@telsasoft.com>
` RE: High process memory consumption when running sort
2022-03-30 10:42 UTC Shai Shapira <Shai.Shapira@Amdocs.com>
[3+ messages in thread]
View taking time to show records
2022-03-24 15:59 UTC Kumar, Mukesh <MKumar@peabodyenergy.com>
` Re: View taking time to show records
2022-03-25 10:20 UTC aditya desai <admad123@gmail.com>
` Re: View taking time to show records
2022-03-25 10:39 UTC hubert depesz lubaczewski <depesz@depesz.com>
` Re: View taking time to show records
2022-03-25 10:43 UTC Laurenz Albe <laurenz.albe@cybertec.at>
` RE: View taking time to show records
2022-03-25 14:07 UTC Kumar, Mukesh <MKumar@peabodyenergy.com>
` Re: View taking time to show records
2022-03-26 04:37 UTC Laurenz Albe <laurenz.albe@cybertec.at>
[6+ messages in thread]
Performance issue post upgrade on Version 13 - Incorrect Estimation Cost choosing Hash Aggregate-Nested Left Loop Join
2022-03-21 11:45 UTC Prajna Shetty <Prajna.Shetty@mindtree.com>
` Re: Performance issue post upgrade on Version 13 - Incorrect Estimation Cost choosing Hash Aggregate-Nested Left Loop Join
2022-03-21 13:59 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Performance issue post upgrade on Version 13 - Incorrect Estimation Cost choosing Hash Aggregate-Nested Left Loop Join
2022-03-22 12:57 UTC Prajna Shetty <Prajna.Shetty@mindtree.com>
` Re: Performance issue post upgrade on Version 13 - Incorrect Estimation Cost choosing Hash Aggregate-Nested Left Loop Join
2022-03-24 11:55 UTC Tomas Vondra <tomas.vondra@enterprisedb.com>
` Re: Performance issue post upgrade on Version 13 - Incorrect Estimation Cost choosing Hash Aggregate-Nested Left Loop Join
2022-03-24 12:24 UTC Justin Pryzby <pryzby@telsasoft.com>
[5+ messages in thread]
Using system tables directly takes many hours, using temp tables with no indexes takes a few seconds for geometry_columns view.
2022-03-23 09:44 UTC Lars Aksel Opsahl <Lars.Opsahl@nibio.no>
` Re: Using system tables directly takes many hours, using temp tables with no indexes takes a few seconds for geometry_columns view.
2022-03-23 12:56 UTC Lars Aksel Opsahl <Lars.Opsahl@nibio.no>
` Re: Using system tables directly takes many hours, using temp tables with no indexes takes a few seconds for geometry_columns view.
2022-03-23 13:19 UTC Justin Pryzby <pryzby@telsasoft.com>
` Re: Using system tables directly takes many hours, using temp tables with no indexes takes a few seconds for geometry_columns view.
2022-03-23 14:49 UTC Lars Aksel Opsahl <Lars.Opsahl@nibio.no>
` Re: Using system tables directly takes many hours, using temp tables with no indexes takes a few seconds for geometry_columns view.
2022-03-24 09:39 UTC Lars Aksel Opsahl <Lars.Opsahl@nibio.no>
[5+ messages in thread]
Optimal configuration for server
2022-03-07 11:51 UTC Luiz Felipph <luizfelipph@gmail.com>
` Re: Optimal configuration for server
2022-03-07 16:51 UTC Ranier Vilela <ranier.vf@gmail.com>
` Re: Optimal configuration for server
2022-03-07 17:17 UTC Luiz Felipph <luizfelipph@gmail.com>
` Re: Optimal configuration for server
2022-03-07 17:39 UTC Ranier Vilela <ranier.vf@gmail.com>
` Re: Optimal configuration for server
2022-03-07 18:07 UTC Tomas Vondra <tomas.vondra@enterprisedb.com>
` Re: Optimal configuration for server
2022-03-07 21:07 UTC Luiz Felipph <luizfelipph@gmail.com>
` Re: Optimal configuration for server
2022-03-07 22:28 UTC Ranier Vilela <ranier.vf@gmail.com>
` Re: Optimal configuration for server
2022-03-08 06:44 UTC Justin Pryzby <pryzby@telsasoft.com>
` Re: Optimal configuration for server
2022-03-12 01:00 UTC Moises Lopez <moylop260@vauxoo.com>
` RE: Optimal configuration for server
2022-03-16 14:01 UTC Michel SALAIS <msalais@msym.fr>
[10+ messages in thread]
Explain analyse with track_io_timing
2022-03-10 05:10 UTC Jayadevan M <maymala.jayadevan@gmail.com>
` Re: Explain analyse with track_io_timing
2022-03-10 06:05 UTC Julien Rouhaud <rjuju123@gmail.com>
` Re: Explain analyse with track_io_timing
2022-03-10 06:10 UTC Jayadevan M <maymala.jayadevan@gmail.com>
[3+ 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