pg.ddx.io pgsql-performance@postgresql.org mailing list archive
help / color / mirror / Atom feedEntire index scanned, but only when in SQL function?
2023-07-11 16:07 UTC Philip Semanchuk <philip@americanefficient.com>
Why is query performance on RLS enabled Postgres worse?
2023-07-10 06:03 UTC Akash Anand <akash@hasura.io>
` Re: Why is query performance on RLS enabled Postgres worse?
2023-07-10 07:01 UTC Akash Anand <akash@hasura.io>
[2+ messages in thread]
Helping planner to chose sequential scan when it improves performance
2023-06-13 19:24 UTC Patrick O'Toole <patrick.otoole@sturdy.ai>
` Re: Helping planner to chose sequential scan when it improves performance
2023-06-14 23:00 UTC Ruslan Zakirov <ruslan.zakirov@gmail.com>
` Fwd: Helping planner to chose sequential scan when it improves performance
2023-06-25 06:29 UTC Patrick O'Toole <patrick.otoole@sturdy.ai>
` Re: Helping planner to chose sequential scan when it improves performance
2023-06-25 19:34 UTC Jeff Janes <jeff.janes@gmail.com>
` Re: Helping planner to chose sequential scan when it improves performance
2023-06-25 19:48 UTC David Rowley <dgrowleyml@gmail.com>
` Re: Helping planner to chose sequential scan when it improves performance
2023-06-27 12:47 UTC Jeff Janes <jeff.janes@gmail.com>
[6+ messages in thread]
extended statistics n-distinct on multiple columns not used when join two tables
2023-06-13 09:21 UTC James Pang (chaolpan) <chaolpan@cisco.com>
` Re: extended statistics n-distinct on multiple columns not used when join two tables
2023-06-13 09:29 UTC Pavel Stehule <pavel.stehule@gmail.com>
` Re: extended statistics n-distinct on multiple columns not used when join two tables
2023-06-13 11:25 UTC David Rowley <dgrowleyml@gmail.com>
` Re: extended statistics n-distinct on multiple columns not used when join two tables
2023-06-13 11:28 UTC Pavel Stehule <pavel.stehule@gmail.com>
` RE: extended statistics n-distinct on multiple columns not used when join two tables
2023-06-13 11:32 UTC James Pang (chaolpan) <chaolpan@cisco.com>
` Re: extended statistics n-distinct on multiple columns not used when join two tables
2023-06-22 00:53 UTC David Rowley <dgrowleyml@gmail.com>
[6+ messages in thread]
Merge David and Goliath tables efficiently
2023-06-17 13:48 UTC Nicolas Paris <nicolas.paris@riseup.net>
` Re: Merge David and Goliath tables efficiently
2023-06-17 19:52 UTC Tomas Vondra <tomas.vondra@enterprisedb.com>
` Re: Merge David and Goliath tables efficiently
2023-06-17 21:42 UTC nicolas paris <nicolas.paris@riseup.net>
` Re: Merge David and Goliath tables efficiently
2023-06-17 23:48 UTC Tomas Vondra <tomas.vondra@enterprisedb.com>
` Re: Merge David and Goliath tables efficiently
2023-06-18 20:57 UTC nicolas paris <nicolas.paris@riseup.net>
` Re: Merge David and Goliath tables efficiently
2023-06-19 07:46 UTC Alvaro Herrera <alvherre@alvh.no-ip.org>
` Re: Merge David and Goliath tables efficiently
2023-06-19 11:34 UTC Tomas Vondra <tomas.vondra@enterprisedb.com>
` Re: Merge David and Goliath tables efficiently
2023-06-19 11:53 UTC Tomas Vondra <tomas.vondra@enterprisedb.com>
` Re: Merge David and Goliath tables efficiently
2023-06-19 12:09 UTC nicolas paris <nicolas.paris@riseup.net>
` Re: Merge David and Goliath tables efficiently
2023-06-19 12:20 UTC nicolas paris <nicolas.paris@riseup.net>
` Re: Merge David and Goliath tables efficiently
2023-06-19 13:13 UTC Tomas Vondra <tomas.vondra@enterprisedb.com>
` Re: Merge David and Goliath tables efficiently
2023-06-19 15:45 UTC nicolas paris <nicolas.paris@riseup.net>
` Re: Merge David and Goliath tables efficiently
2023-06-19 23:25 UTC Tomas Vondra <tomas.vondra@enterprisedb.com>
` Re: Merge David and Goliath tables efficiently
2023-06-20 10:02 UTC nicolas paris <nicolas.paris@riseup.net>
` Re: Merge David and Goliath tables efficiently
2023-06-20 12:45 UTC Tomas Vondra <tomas.vondra@enterprisedb.com>
[15+ messages in thread]
Index on (fixed size) bytea value
2023-06-19 20:05 UTC Les <nagylzs@gmail.com>
` Re: Index on (fixed size) bytea value
2023-06-19 20:30 UTC David G. Johnston <david.g.johnston@gmail.com>
` Re: Index on (fixed size) bytea value
2023-06-20 06:13 UTC Les <nagylzs@gmail.com>
` Re: Index on (fixed size) bytea value
2023-06-20 06:50 UTC Laurenz Albe <laurenz.albe@cybertec.at>
` Re: Index on (fixed size) bytea value
2023-06-20 07:18 UTC Les <nagylzs@gmail.com>
[5+ messages in thread]
Forced to use UNION ALL when having multiple ANY operators and ORDER BY LIMIT
2023-06-12 20:17 UTC benoit <benoit@hopsandfork.com>
` Re: Forced to use UNION ALL when having multiple ANY operators and ORDER BY LIMIT
2023-06-12 20:34 UTC Peter Geoghegan <pg@bowt.ie>
` RE: Forced to use UNION ALL when having multiple ANY operators and ORDER BY LIMIT
2023-06-12 20:50 UTC benoit <benoit@hopsandfork.com>
` Re: Forced to use UNION ALL when having multiple ANY operators and ORDER BY LIMIT
2023-06-12 20:55 UTC Chris Hoover <chrish@aweber.com>
` RE: Forced to use UNION ALL when having multiple ANY operators and ORDER BY LIMIT
2023-06-12 21:34 UTC benoit <benoit@hopsandfork.com>
` Re: Forced to use UNION ALL when having multiple ANY operators and ORDER BY LIMIT
2023-06-13 00:09 UTC Chris Hoover <chrish@aweber.com>
` RE: Forced to use UNION ALL when having multiple ANY operators and ORDER BY LIMIT
2023-06-18 21:23 UTC msalais@msym.fr
` Re: Forced to use UNION ALL when having multiple ANY operators and ORDER BY LIMIT
2023-06-19 16:30 UTC Benoit Tigeot <benoit@hopsandfork.com>
[8+ messages in thread]
Postgresql equal join on function with columns not use index
2023-06-12 08:09 UTC James Pang (chaolpan) <chaolpan@cisco.com>
` Re: Postgresql equal join on function with columns not use index
2023-06-12 13:18 UTC Tom Lane <tgl@sss.pgh.pa.us>
` RE: Postgresql equal join on function with columns not use index
2023-06-12 14:20 UTC James Pang (chaolpan) <chaolpan@cisco.com>
` Re: Postgresql equal join on function with columns not use index
2023-06-13 13:50 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: Postgresql equal join on function with columns not use index
2023-06-13 14:17 UTC Pavel Stehule <pavel.stehule@gmail.com>
` Re: Postgresql equal join on function with columns not use index
2023-06-13 15:00 UTC Pavel Stehule <pavel.stehule@gmail.com>
` RE: Postgresql equal join on function with columns not use index
2023-06-15 08:32 UTC James Pang (chaolpan) <chaolpan@cisco.com>
` Re: Postgresql equal join on function with columns not use index
2023-06-15 08:35 UTC Pavel Stehule <pavel.stehule@gmail.com>
[8+ messages in thread]
wrong rows estimation by hash join
2023-06-09 08:36 UTC James Pang (chaolpan) <chaolpan@cisco.com>
` Re: wrong rows estimation by hash join
2023-06-10 20:38 UTC Tomas Vondra <tomas.vondra@enterprisedb.com>
[2+ messages in thread]
Weird behavior of INSERT QUERY
2023-06-04 08:34 UTC Satalabaha Postgres <satalabaha.postgres@gmail.com>
` Re: Weird behavior of INSERT QUERY
2023-06-04 08:40 UTC Satalabaha Postgres <satalabaha.postgres@gmail.com>
` Re: Weird behavior of INSERT QUERY
2023-06-04 11:21 UTC Julien Rouhaud <rjuju123@gmail.com>
` Re: Weird behavior of INSERT QUERY
2023-06-04 11:42 UTC Satalabaha Postgres <satalabaha.postgres@gmail.com>
` Re: Weird behavior of INSERT QUERY
2023-06-04 13:21 UTC Julien Rouhaud <rjuju123@gmail.com>
` Re: Weird behavior of INSERT QUERY
2023-06-04 13:26 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: Weird behavior of INSERT QUERY
2023-06-04 14:16 UTC Ranier Vilela <ranier.vf@gmail.com>
` Re: Weird behavior of INSERT QUERY
2023-06-04 14:49 UTC Satalabaha Postgres <satalabaha.postgres@gmail.com>
` Re: Weird behavior of INSERT QUERY
2023-06-04 14:58 UTC Satalabaha Postgres <satalabaha.postgres@gmail.com>
` Re: Weird behavior of INSERT QUERY
2023-06-04 23:05 UTC Ranier Vilela <ranier.vf@gmail.com>
` Re: Weird behavior of INSERT QUERY
2023-06-05 11:55 UTC Satalabaha Postgres <satalabaha.postgres@gmail.com>
[11+ messages in thread]
Understand time taken by individual SQL statements in a procedure
2023-06-03 07:18 UTC Satalabaha Postgres <satalabaha.postgres@gmail.com>
` Re: Understand time taken by individual SQL statements in a procedure
2023-06-03 07:36 UTC Julien Rouhaud <rjuju123@gmail.com>
` Re: Understand time taken by individual SQL statements in a procedure
2023-06-03 17:46 UTC Satalabaha Postgres <satalabaha.postgres@gmail.com>
[3+ messages in thread]
thousands of CachedPlan entry per backend
2023-06-01 03:36 UTC James Pang (chaolpan) <chaolpan@cisco.com>
` Re: thousands of CachedPlan entry per backend
2023-06-01 06:53 UTC Laurenz Albe <laurenz.albe@cybertec.at>
` Re: thousands of CachedPlan entry per backend
2023-06-01 07:18 UTC Pavel Stehule <pavel.stehule@gmail.com>
` RE: thousands of CachedPlan entry per backend
2023-06-01 08:50 UTC James Pang (chaolpan) <chaolpan@cisco.com>
` Re: thousands of CachedPlan entry per backend
2023-06-01 12:48 UTC Laurenz Albe <laurenz.albe@cybertec.at>
` RE: thousands of CachedPlan entry per backend
2023-06-02 01:45 UTC James Pang (chaolpan) <chaolpan@cisco.com>
` Re: thousands of CachedPlan entry per backend
2023-06-02 04:56 UTC Pavel Stehule <pavel.stehule@gmail.com>
` RE: thousands of CachedPlan entry per backend
2023-06-02 09:06 UTC James Pang (chaolpan) <chaolpan@cisco.com>
` Re: thousands of CachedPlan entry per backend
2023-06-02 19:17 UTC Jeff Janes <jeff.janes@gmail.com>
[9+ messages in thread]
How to reduce latency with fast short queries in Postgresql 15.3 on a NUMA server
2023-05-31 12:40 UTC Sergio Rus <geiros@gmail.com>
` Re: How to reduce latency with fast short queries in Postgresql 15.3 on a NUMA server
2023-05-31 13:47 UTC Kenneth Marshall <ktm@rice.edu>
` Re: How to reduce latency with fast short queries in Postgresql 15.3 on a NUMA server
2023-05-31 16:03 UTC Sergio Rus <geiros@gmail.com>
` Re: How to reduce latency with fast short queries in Postgresql 15.3 on a NUMA server
2023-05-31 17:17 UTC Imre Samu <pella.samu@gmail.com>
` Re: How to reduce latency with fast short queries in Postgresql 15.3 on a NUMA server
2023-05-31 17:54 UTC Andres Freund <andres@anarazel.de>
` Re: How to reduce latency with fast short queries in Postgresql 15.3 on a NUMA server
2023-05-31 18:16 UTC Ranier Vilela <ranier.vf@gmail.com>
` Re: How to reduce latency with fast short queries in Postgresql 15.3 on a NUMA server
2023-06-01 14:26 UTC Sergio Rus <geiros@gmail.com>
[7+ messages in thread]
Unaccounted regression from postgresql 11 in later versions
2023-05-31 08:43 UTC Bob Jolliffe <bobjolliffe@gmail.com>
` Re: Unaccounted regression from postgresql 11 in later versions
2023-05-31 10:11 UTC Michael Christofides <michael@pgmustard.com>
` Re: Unaccounted regression from postgresql 11 in later versions
2023-05-31 10:26 UTC Bob Jolliffe <bobjolliffe@gmail.com>
[3+ messages in thread]
Fsync IO issue
2023-05-04 17:31 UTC ProfiVPS Support <support@profivps.hu>
` Re: Fsync IO issue
2023-05-04 17:41 UTC ProfiVPS Support <support@profivps.hu>
` Re: Fsync IO issue
2023-05-04 19:21 UTC Andres Freund <andres@anarazel.de>
` Re: Fsync IO issue
2023-05-04 20:37 UTC ProfiVPS Support <support@profivps.hu>
` Re: Fsync IO issue
2023-05-04 21:23 UTC Thomas Munro <thomas.munro@gmail.com>
` Re: Fsync IO issue
2023-05-30 20:56 UTC Merlin Moncure <mmoncure@gmail.com>
[6+ messages in thread]
PostgreSQL performance on ARM i.MX6
2023-05-23 11:42 UTC Druckenmueller, Marc <marc.druckenmueller@philips.com>
` Re: PostgreSQL performance on ARM i.MX6
2023-05-23 13:25 UTC Daniele Varrazzo <daniele.varrazzo@gmail.com>
` Re: PostgreSQL performance on ARM i.MX6
2023-05-23 16:29 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: PostgreSQL performance on ARM i.MX6
2023-05-23 19:46 UTC Richard Huxton <richard@huxton.org.uk>
` Re: PostgreSQL performance on ARM i.MX6
2023-05-23 19:56 UTC Ranier Vilela <ranier.vf@gmail.com>
[5+ messages in thread]
Connection drops on postgres 11.16
2023-05-11 18:40 UTC aditya desai <admad123@gmail.com>
Performance issues in query with multiple joins
2023-04-28 12:19 UTC Παρασκευη Πασσαρη <passari.paraskevi@gmail.com>
` Performance issues in query with multiple joins
2023-04-28 13:03 UTC David G. Johnston <david.g.johnston@gmail.com>
` Re: Performance issues in query with multiple joins
2023-04-28 14:07 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: Performance issues in query with multiple joins
2023-05-01 04:15 UTC Laurenz Albe <laurenz.albe@cybertec.at>
[4+ messages in thread]
Postgres Metrics
2023-04-15 11:04 UTC André Rodrigues <db.andre@gmail.com>
` Re: Postgres Metrics
2023-04-15 14:53 UTC Joe Conway <mail@joeconway.com>
` Re: Postgres Metrics
2023-04-24 08:23 UTC Jesper Pedersen <jesper.pedersen@redhat.com>
[3+ messages in thread]
How do Monitoring tools capture explain plan of a query
2023-04-22 15:28 UTC kunwar singh <krishsingh.111@gmail.com>
` Re: How do Monitoring tools capture explain plan of a query
2023-04-22 16:17 UTC kyle Hailey <kylelf@gmail.com>
` Re: How do Monitoring tools capture explain plan of a query
2023-04-23 19:28 UTC kunwar singh <krishsingh.111@gmail.com>
[3+ messages in thread]
speeding up grafana sensor-data query on raspberry pi 3
2023-04-16 17:00 UTC Clemens Eisserer <linuxhippy@gmail.com>
` Re: speeding up grafana sensor-data query on raspberry pi 3
2023-04-16 17:15 UTC Justin Pryzby <pryzby@telsasoft.com>
` Re: speeding up grafana sensor-data query on raspberry pi 3
2023-04-16 20:50 UTC David Rowley <dgrowleyml@gmail.com>
` Re: speeding up grafana sensor-data query on raspberry pi 3
2023-04-16 22:10 UTC Andres Freund <andres@anarazel.de>
` Re: speeding up grafana sensor-data query on raspberry pi 3
2023-04-17 19:06 UTC Luiz Felipph <luizfelipph@gmail.com>
` Re: speeding up grafana sensor-data query on raspberry pi 3
2023-04-18 12:14 UTC Clemens Eisserer <linuxhippy@gmail.com>
` Re: speeding up grafana sensor-data query on raspberry pi 3
2023-04-20 16:39 UTC Clemens Eisserer <linuxhippy@gmail.com>
[7+ messages in thread]
What is equivalent of v$sesstat and v$sql_plan in postgres?
2023-04-20 13:37 UTC kunwar singh <krishsingh.111@gmail.com>
` Re: What is equivalent of v$sesstat and v$sql_plan in postgres?
2023-04-20 13:40 UTC MichaelDBA <MichaelDBA@sqlexec.com>
[2+ messages in thread]
High QPS, random index writes and vacuum
2023-04-18 00:35 UTC peter plachta <pplachta@gmail.com>
` Re: High QPS, random index writes and vacuum
2023-04-18 00:38 UTC Peter Geoghegan <pg@bowt.ie>
` Re: High QPS, random index writes and vacuum
2023-04-18 02:01 UTC Tom Lane <tgl@sss.pgh.pa.us>
` Re: High QPS, random index writes and vacuum
2023-04-18 02:40 UTC David Rowley <dgrowleyml@gmail.com>
` Re: High QPS, random index writes and vacuum
2023-04-18 02:43 UTC peter plachta <pplachta@gmail.com>
` Re: High QPS, random index writes and vacuum
2023-04-18 02:44 UTC peter plachta <pplachta@gmail.com>
` Re: High QPS, random index writes and vacuum
2023-04-18 02:49 UTC Thomas Munro <thomas.munro@gmail.com>
` Re: High QPS, random index writes and vacuum
2023-04-18 02:52 UTC Peter Geoghegan <pg@bowt.ie>
[8+ messages in thread]
time sorted UUIDs
2022-12-14 21:56 UTC Tim Jones <tim.jones@mccarthy.co.nz>
` Re: time sorted UUIDs
2022-12-15 11:59 UTC Laurenz Albe <laurenz.albe@cybertec.at>
` Re: time sorted UUIDs
2022-12-15 12:05 UTC Adrien Nayrat <adrien.nayrat@anayrat.info>
` Re: time sorted UUIDs
2023-04-18 00:25 UTC peter plachta <pplachta@gmail.com>
[4+ messages in thread]
Replication lag due to lagging restart_lsn
2020-08-18 16:27 UTC Satyam Shekhar <satyamshekhar@gmail.com>
` Re: Replication lag due to lagging restart_lsn
2020-08-19 11:43 UTC Kyotaro Horiguchi <horikyota.ntt@gmail.com>
` Re: Replication lag due to lagging restart_lsn
2020-08-19 13:15 UTC Kiran Singh <kiranjanarthan24@gmail.com>
` Re: Replication lag due to lagging restart_lsn
2023-04-11 03:39 UTC milist ujang <ujang.milist@gmail.com>
` Re: Replication lag due to lagging restart_lsn
2023-04-15 10:41 UTC milist ujang <ujang.milist@gmail.com>
[5+ 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