pg.ddx.io  pgsql-performance@postgresql.org mailing list archive  
help / color / mirror / Atom feed
Huge generated UNION ALL faster than JOIN?
  2019-05-12 14:08 UTC  Ancoron Luciferis <ancoron.luciferis@googlemail.com>
` Re: Huge generated UNION ALL faster than JOIN?
  2019-05-12 18:08 UTC  Tom Lane <tgl@sss.pgh.pa.us>
` Re: Huge generated UNION ALL faster than JOIN?
  2019-05-12 22:23 UTC  Ancoron Luciferis <ancoron.luciferis@googlemail.com>
  [3+ messages in thread]

integrate Postgres Users Authentication with our own LDAP Server
  2019-05-09 04:51 UTC  M Tarkeshwar Rao <m.tarkeshwar.rao@ericsson.com>
` Re: integrate Postgres Users Authentication with our own LDAP Server
  2019-05-09 06:17 UTC  Achilleas Mantzios <achill@matrix.gatewaynet.com>
` Re: integrate Postgres Users Authentication with our own LDAP Server
  2019-05-09 06:42 UTC  Laurenz Albe <laurenz.albe@cybertec.at>
` RE: integrate Postgres Users Authentication with our own LDAP Server
  2019-05-09 07:11 UTC  M Tarkeshwar Rao <m.tarkeshwar.rao@ericsson.com>
` Re: integrate Postgres Users Authentication with our own LDAP Server
  2019-05-09 07:23 UTC  Laurenz Albe <laurenz.albe@cybertec.at>
` Re: integrate Postgres Users Authentication with our own LDAP Server
  2019-05-09 12:43 UTC  Tomas Vondra <tomas.vondra@2ndquadrant.com>
` Re: integrate Postgres Users Authentication with our own LDAP Server
  2019-05-09 19:24 UTC  Stephen Frost <sfrost@snowman.net>
  [7+ messages in thread]

GCC 8.3.0 vs. 9.0.1
  2019-05-07 16:14 UTC  Steven Winfield <Steven.Winfield@cantabcapital.com>
` Re: GCC 8.3.0 vs. 9.0.1
  2019-05-07 17:05 UTC  Tom Lane <tgl@sss.pgh.pa.us>
` Re: GCC 8.3.0 vs. 9.0.1
  2019-05-07 17:28 UTC  Peter Geoghegan <pg@bowt.ie>
` Re: GCC 8.3.0 vs. 9.0.1
  2019-05-07 17:32 UTC  Andres Freund <andres@anarazel.de>
` Re: GCC 8.3.0 vs. 9.0.1
  2019-05-07 17:42 UTC  Andres Freund <andres@anarazel.de>
` Re: GCC 8.3.0 vs. 9.0.1
  2019-05-07 18:04 UTC  Andres Freund <andres@anarazel.de>
` RE: GCC 8.3.0 vs. 9.0.1
  2019-05-09 14:04 UTC  Steven Winfield <Steven.Winfield@cantabcapital.com>
  [7+ messages in thread]

PostgreSQL optimizer use seq scan instead of pkey index only scan (in queries with postgres_fdw)
  2019-05-06 14:43 UTC  Vitaly Baranovsky <barvetalforums@gmail.com>
` Re: PostgreSQL optimizer use seq scan instead of pkey index only scan (in queries with postgres_fdw)
  2019-05-06 15:32 UTC  Jeff Janes <jeff.janes@gmail.com>
` Re: PostgreSQL optimizer use seq scan instead of pkey index only scan (in queries with postgres_fdw)
  2019-05-06 15:38 UTC  Vitaly Baranovsky <barvetalforums@gmail.com>
` Re: PostgreSQL optimizer use seq scan instead of pkey index only scan (in queries with postgres_fdw)
  2019-05-06 15:53 UTC  Tom Lane <tgl@sss.pgh.pa.us>
` Re: PostgreSQL optimizer use seq scan instead of pkey index only scan (in queries with postgres_fdw)
  2019-05-06 15:53 UTC  Jeff Janes <jeff.janes@gmail.com>
` Re: PostgreSQL optimizer use seq scan instead of pkey index only scan (in queries with postgres_fdw)
  2019-05-06 16:36 UTC  Vitaly Baranovsky <barvetalforums@gmail.com>
` Re: PostgreSQL optimizer use seq scan instead of pkey index only scan (in queries with postgres_fdw)
  2019-05-06 17:17 UTC  Jeff Janes <jeff.janes@gmail.com>
  [7+ messages in thread]

LIMIT confuses the planner
  2009-02-23 12:26 UTC  Kouber Saparev <kouber@saparev.com>
` Re: LIMIT confuses the planner
  2009-02-23 13:27 UTC  Richard Huxton <dev@archonet.com>
` Re: LIMIT confuses the planner
  2009-02-23 14:53 UTC  Robert Haas <robertmhaas@gmail.com>
` Re: LIMIT confuses the planner
  2009-02-23 15:09 UTC  Tom Lane <tgl@sss.pgh.pa.us>
` Re: LIMIT confuses the planner
  2009-02-23 17:42 UTC  Kouber Saparev <kouber@saparev.com>
` Re: LIMIT confuses the planner
  2009-02-23 18:01 UTC  Tom Lane <tgl@sss.pgh.pa.us>
` Re: LIMIT confuses the planner
  2009-02-23 18:44 UTC  Kouber Saparev <kouber@saparev.com>
` Re: LIMIT confuses the planner
  2009-02-24 17:08 UTC  Kouber Saparev <kouber@saparev.com>
` Re: LIMIT confuses the planner
  2009-03-22 21:29 UTC  Tom Lane <tgl@sss.pgh.pa.us>
` Re: LIMIT confuses the planner
  2009-03-23 00:12 UTC  marcin mank <marcin.mank@gmail.com>
` Re: LIMIT confuses the planner
  2009-03-23 00:56 UTC  marcin mank <marcin.mank@gmail.com>
` Re: LIMIT confuses the planner
  2009-03-23 02:18 UTC  Tom Lane <tgl@sss.pgh.pa.us>
` Re: LIMIT confuses the planner
  2009-03-24 10:52 UTC  Kouber Saparev <kouber@saparev.com>
` Oracle to postgres migration
  2019-04-08 10:23 UTC  Daulat Ram <Daulat.Ram@exponential.com>
  [14+ messages in thread]

monitoring options for postgresql under AWS/RDS?
  2019-04-04 16:28 UTC  Mamet, Eric (GfK) <Eric.Mamet@gfk.com>
` Re: monitoring options for postgresql under AWS/RDS?
  2019-04-04 17:43 UTC  Justin Pryzby <pryzby@telsasoft.com>
` Re: monitoring options for postgresql under AWS/RDS?
  2019-04-04 18:03 UTC  Rijo Roy <rjo_roy@yahoo.com>
` RE: monitoring options for postgresql under AWS/RDS?
  2019-04-05 09:46 UTC  Mamet, Eric (GfK) <Eric.Mamet@gfk.com>
  [4+ messages in thread]

Re: RAM usage of PostgreSql
  2019-04-04 17:46 UTC  Justin Pryzby <pryzby@telsasoft.com>
` Re: RAM usage of PostgreSql
  2019-04-04 18:09 UTC  Keith <keith@keithf4.com>
  [2+ messages in thread]

Commit(?) overhead
  2019-04-03 21:59 UTC  Duncan Kinnear <duncan.kinnear@mccarthy.co.nz>
` Re: Commit(?) overhead
  2019-04-04 15:14 UTC  Jeff Janes <jeff.janes@gmail.com>
  [2+ messages in thread]

trying to analyze deadlock
  2019-03-27 12:52 UTC  Mariel Cherkassky <mariel.cherkassky@gmail.com>
` Re: trying to analyze deadlock
  2019-03-27 13:17 UTC  Laurenz Albe <laurenz.albe@cybertec.at>
` Re: trying to analyze deadlock
  2019-03-27 13:19 UTC  Laurenz Albe <laurenz.albe@cybertec.at>
` Fwd: trying to analyze deadlock
  2019-04-01 10:16 UTC  Mariel Cherkassky <mariel.cherkassky@gmail.com>
` Re: trying to analyze deadlock
  2019-04-01 11:20 UTC  Mariel Cherkassky <mariel.cherkassky@gmail.com>
` Re: trying to analyze deadlock
  2019-04-02 12:21 UTC  Shreeyansh Dba <shreeyansh2014@gmail.com>
  [6+ messages in thread]

(no subject)
  2019-04-02 08:32 UTC  Mariel Cherkassky <mariel.cherkassky@gmail.com>

Postgresql Sort cost Poor performance?
  2019-04-01 09:45 UTC  tank.zhang <6220104@qq.com>
` Re: Postgresql Sort cost Poor performance?
  2019-04-01 10:20 UTC  Andrew Gierth <andrew@tao11.riddles.org.uk>
` Re: Postgresql Sort cost Poor performance?
  2019-04-01 10:30 UTC  tank.zhang <6220104@qq.com>
` Re: Postgresql Sort cost Poor performance?
  2019-04-01 10:32 UTC  Gavin Flower <GavinFlower@archidevsys.co.nz>
` Re: Postgresql Sort cost Poor performance?
  2019-04-01 10:54 UTC  Christoph Berg <myon@debian.org>
` Re: Postgresql Sort cost Poor performance?
  2019-04-02 05:25 UTC  Ramón Bastidas <ramon.r.bastidas@gmail.com>
` Re: Postgresql Sort cost Poor performance?
  2019-04-02 07:00 UTC  tank.zhang <6220104@qq.com>
` Re: Postgresql Sort cost Poor performance?
  2019-04-02 07:42 UTC  David Rowley <david.rowley@2ndquadrant.com>
` Re: Postgresql Sort cost Poor performance?
  2019-04-02 08:23 UTC  tank.zhang <6220104@qq.com>
  [9+ messages in thread]

Query performance over a large proportion of data
  2009-03-10 21:12 UTC  Steve McLellan <smclellan@mintel.com>
` Re: Query performance over a large proportion of data
  2009-03-10 21:57 UTC  Scott Marlowe <scott.marlowe@gmail.com>
` Re: Query performance over a large proportion of data
  2009-03-10 22:06 UTC  Kevin Grittner <Kevin.Grittner@wicourts.gov>
` Re: Query performance over a large proportion of data
  2009-03-10 23:19 UTC  Scott Marlowe <scott.marlowe@gmail.com>
` Re: Query performance over a large proportion of data
  2009-03-11 00:09 UTC  Tom Lane <tgl@sss.pgh.pa.us>
` Re: Query performance over a large proportion of data
  2009-03-11 00:16 UTC  Tom Lane <tgl@sss.pgh.pa.us>
` Re: Query performance over a large proportion of data
  2009-03-11 03:15 UTC  Steve McLellan <smclellan@mintel.com>
` Re: Query performance over a large proportion of data
  2009-03-11 03:21 UTC  Steve McLellan <smclellan@mintel.com>
` Re: Query performance over a large proportion of data
  2009-03-11 03:30 UTC  Steve McLellan <smclellan@mintel.com>
` Re: Query performance over a large proportion of data
  2009-03-11 04:53 UTC  Scott Marlowe <scott.marlowe@gmail.com>
` Re: Query performance over a large proportion of data
  2009-03-14 14:47 UTC  decibel <decibel@decibel.org>
` Re: Query performance over a large proportion of data
  2009-03-15 02:38 UTC  Matteo Beccati <php@beccati.com>
` Good afternoon.
  2019-03-06 20:09 UTC  Kenia Vergara <vergarakenia@gmail.com>
` Re: Good afternoon.
  2019-04-01 13:03 UTC  Rafia Sabih <rafia.pghackers@gmail.com>
` Re: Good afternoon.
  2019-04-02 05:03 UTC  Ramón Bastidas <ramon.r.bastidas@gmail.com>
  [15+ messages in thread]

LIMIT OFFSET with DB view vs plain SQL
  2019-03-28 22:41 UTC  Raj Gandhi <raj01gandhi@gmail.com>
` Re: LIMIT OFFSET with DB view vs plain SQL
  2019-03-28 22:43 UTC  Raj Gandhi <raj01gandhi@gmail.com>
` Re: LIMIT OFFSET with DB view vs plain SQL
  2019-03-29 13:53 UTC  Laurenz Albe <laurenz.albe@cybertec.at>
` Re: LIMIT OFFSET with DB view vs plain SQL
  2019-03-29 15:28 UTC  Merlin Moncure <mmoncure@gmail.com>
` Re: LIMIT OFFSET with DB view vs plain SQL
  2019-03-29 23:38 UTC  Raj Gandhi <raj01gandhi@gmail.com>
` Re: LIMIT OFFSET with DB view vs plain SQL
  2019-04-01 13:56 UTC  Raj Gandhi <raj01gandhi@gmail.com>
` Re: LIMIT OFFSET with DB view vs plain SQL
  2019-04-02 02:06 UTC  Raj Gandhi <raj01gandhi@gmail.com>
` Re: LIMIT OFFSET with DB view vs plain SQL
  2019-04-02 04:16 UTC  SAMEER KUMAR <sameer.kasi200x@gmail.com>
` Re: LIMIT OFFSET with DB view vs plain SQL
  2019-04-02 04:49 UTC  Ramón Bastidas <ramon.r.bastidas@gmail.com>
  [9+ messages in thread]

Need advice: Parallel query execution introduces performance regression
  2019-03-29 16:06 UTC  Jinho Jung <jinhojun@usc.edu>

endless quere when upsert with ON CONFLICT clause
  2019-03-29 14:29 UTC  Stephan Schmidt <schmidt@dltmail.de>
` Re: endless quere when upsert with ON CONFLICT clause
  2019-03-29 16:00 UTC  Andreas Kretschmer <andreas@a-kretschmer.de>
  [2+ messages in thread]

When does sequential performance matter in PG?
  2009-03-10 14:09 UTC  henk de wit <henk53602@hotmail.com>
` Re: When does sequential performance matter in PG?
  2009-03-10 14:28 UTC  Matthew Wakeling <matthew@flymine.org>
` Re: When does sequential performance matter in PG?
  2009-03-10 14:57 UTC  henk de wit <henk53602@hotmail.com>
` Re: When does sequential performance matter in PG?
  2009-03-10 17:50 UTC  Greg Smith <gsmith@gregsmith.com>
` Re: When does sequential performance matter in PG?
  2009-03-10 18:01 UTC  Scott Carey <scott@richrelevance.com>
` Scale out postgresql
  2019-03-28 10:10 UTC  Mariel Cherkassky <mariel.cherkassky@gmail.com>
` Re: Scale out postgresql
  2019-03-28 16:10 UTC  Sam R. <samruohola@yahoo.com>
` Re: Scale out postgresql
  2019-03-28 16:19 UTC  Mariel Cherkassky <mariel.cherkassky@gmail.com>
` Re: Scale out postgresql
  2019-03-28 16:26 UTC  Sumedh Pathak <Sumedh.Pathak@microsoft.com>
  [9+ messages in thread]

EXPLAIN PLAN for DELETE CASCADE or DELETE not using pkey index despite EXPLAINing that it would?
  2019-03-21 19:31 UTC  Gunther <raj@gusw.net>
` Re: EXPLAIN PLAN for DELETE CASCADE or DELETE not using pkey index despite EXPLAINing that it would?
  2019-03-21 21:16 UTC  Tom Lane <tgl@sss.pgh.pa.us>
` Re: EXPLAIN PLAN for DELETE CASCADE or DELETE not using pkey index despite EXPLAINing that it would?
  2019-03-22 20:01 UTC  Gunther <raj@gusw.net>
` Re: EXPLAIN PLAN for DELETE CASCADE or DELETE not using pkey index despite EXPLAINing that it would?
  2019-03-22 20:07 UTC  Justin Pryzby <pryzby@telsasoft.com>
  [4+ messages in thread]

Poor man's partitioned index .... not being used?
  2019-03-21 02:45 UTC  Gunther <raj@gusw.net>
` Re: Poor man's partitioned index .... not being used?
  2019-03-21 03:34 UTC  David Rowley <david.rowley@2ndquadrant.com>
` Re: Poor man's partitioned index .... not being used?
  2019-03-21 03:46 UTC  Andrew Gierth <andrew@tao11.riddles.org.uk>
` Re: Poor man's partitioned index .... not being used?
  2019-03-21 18:57 UTC  Gunther <raj@gusw.net>
` Re: Poor man's partitioned index .... not being used?
  2019-03-22 12:56 UTC  David Rowley <david.rowley@2ndquadrant.com>
  [5+ messages in thread]

AW: Performance issue with order by clause on
  2019-03-20 21:49 UTC  Stephan Schmidt <schmidt@dltmail.de>

Performance issue with order by clause on
  2019-03-20 11:05 UTC  Maracska Ádám <csuszmusz@gmail.com>
` Re: Performance issue with order by clause on
  2019-03-20 17:34 UTC  Corey Huinker <corey.huinker@gmail.com>
  [2+ messages in thread]

Distributing data over "spindles" even on AWS EBS, (followup to the work queue saga)
  2019-03-13 18:44 UTC  Gunther <raj@gusw.net>
` Re: Distributing data over "spindles" even on AWS EBS, (followup to the work queue saga)
  2019-03-14 14:53 UTC  Gunther <raj@gusw.net>
` Re: Distributing data over "spindles" even on AWS EBS, (followup to the work queue saga)
  2019-03-14 15:11 UTC  Jeremy Schneider <schnjere@amazon.com>
` Re: Distributing data over "spindles" even on AWS EBS, (followup to the work queue saga)
  2019-03-14 15:54 UTC  Justin Pryzby <pryzby@telsasoft.com>
` Re: Distributing data over "spindles" even on AWS EBS, (followup to the work queue saga)
  2019-03-17 18:42 UTC  Gunther <raj@gusw.net>
` Re: Distributing data over "spindles" even on AWS EBS, (followup to the work queue saga)
  2019-03-19 15:18 UTC  Sam Gendler <sgendler@ideasculptor.com>
  [6+ messages in thread]

Facing issue in using special characters
  2019-03-15 05:19 UTC  M Tarkeshwar Rao <m.tarkeshwar.rao@ericsson.com>
` Re: Facing issue in using special characters
  2019-03-15 06:33 UTC  David G. Johnston <david.g.johnston@gmail.com>
` Re: Facing issue in using special characters
  2019-03-15 15:59 UTC  Gunther <raj@gusw.net>
` Re: Facing issue in using special characters
  2019-03-15 19:26 UTC  Chapman Flack <chap@anastigmatix.net>
` Re: Facing issue in using special characters
  2019-03-17 15:01 UTC  Warner, Gary, Jr <gar@uab.edu>
` Re: Facing issue in using special characters
  2019-03-18 21:19 UTC  Peter J. Holzer <hjp-pgsql@hjp.at>
  [6+ messages in thread]

MDRaid or LSI MegaRAID?
  2019-03-16 18:58 UTC  Rory Campbell-Lange <rory@campbell-lange.net>

jsonb_set performance degradation / multiple jsonb_set on multiple documents
  2019-03-15 16:02 UTC  Alexandru Lazarev <alexandru.lazarev@gmail.com>
` Re: jsonb_set performance degradation / multiple jsonb_set on multiple documents
  2019-03-15 16:35 UTC  Michel Pelletier <pelletier.michel@gmail.com>
  [2+ messages in thread]

impact of auto explain on overall performance
  2019-03-14 07:29 UTC  Stephan Schmidt <schmidt@dltmail.de>
` Re: impact of auto explain on overall performance
  2019-03-14 08:23 UTC  Justin Pryzby <pryzby@telsasoft.com>
` Re: impact of auto explain on overall performance
  2019-03-14 09:08 UTC  Adrien NAYRAT <adrien.nayrat@anayrat.info>
` Re: impact of auto explain on overall performance
  2019-03-14 17:50 UTC  Jeff Janes <jeff.janes@gmail.com>
` Re: impact of auto explain on overall performance
  2019-03-14 19:58 UTC  Jeremy Schneider <schneider@ardentperf.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