pg.ddx.io  pgsql-performance@postgresql.org mailing list archive  
help / color / mirror / Atom feed
SSL connection getting rejected on AWS RDS
  2020-09-30 07:19 UTC  aditya desai <admad123@gmail.com>
` Re: SSL connection getting rejected on AWS RDS
  2020-09-30 11:17 UTC  Hannah Huang <hannah.huang.y@gmail.com>
` Re: SSL connection getting rejected on AWS RDS
  2020-09-30 15:50 UTC  aditya desai <admad123@gmail.com>
` Re: SSL connection getting rejected on AWS RDS
  2020-10-01 04:51 UTC  Hannah Huang <hannah.huang.y@gmail.com>
  [4+ messages in thread]

AWS RDS PostgreSQL CPU Spiking to 100%
  2020-09-08 13:33 UTC  aditya desai <admad123@gmail.com>
` Re: AWS RDS PostgreSQL CPU Spiking to 100%
  2020-09-08 14:36 UTC  Pavel Stehule <pavel.stehule@gmail.com>
` Re: AWS RDS PostgreSQL CPU Spiking to 100%
  2020-09-08 16:05 UTC  Jeff Janes <jeff.janes@gmail.com>
` Re: AWS RDS PostgreSQL CPU Spiking to 100%
  2020-09-28 15:51 UTC  aditya desai <admad123@gmail.com>
` Re: AWS RDS PostgreSQL CPU Spiking to 100%
  2020-09-28 16:09 UTC  Prince Pathria <prince.pathria@goevive.com>
` Re: AWS RDS PostgreSQL CPU Spiking to 100%
  2020-09-30 07:13 UTC  aditya desai <admad123@gmail.com>
  [6+ messages in thread]

Is it possible to specify minimum number of rows planner should consider?
  2020-09-28 20:12 UTC  Timothy Garnett <tgarnett@panjiva.com>
` Re: Is it possible to specify minimum number of rows planner should consider?
  2020-09-28 21:06 UTC  Tom Lane <tgl@sss.pgh.pa.us>
` Re: Is it possible to specify minimum number of rows planner should consider?
  2020-09-28 21:45 UTC  Matthew Bellew <matthewb@labkey.com>
` Re: Is it possible to specify minimum number of rows planner should consider?
  2020-09-29 00:22 UTC  Timothy Garnett <tgarnett@panjiva.com>
  [4+ messages in thread]

How to encrypt database password in pgpass or unix file to run batch jobs through shell script
  2020-09-25 09:34 UTC  aditya desai <admad123@gmail.com>
` Re: How to encrypt database password in pgpass or unix file to run batch jobs through shell script
  2020-09-25 19:51 UTC  Bruce Momjian <bruce@momjian.us>
  [2+ messages in thread]

Single column vs composite partial index
  2020-09-15 22:33 UTC  Nagaraj Raj <nagaraj.sf@yahoo.com>
` Re: Single column vs composite partial index
  2020-09-16 04:18 UTC  Justin Pryzby <pryzby@telsasoft.com>
` Re: Single column vs composite partial index
  2020-09-16 06:59 UTC  Nagaraj Raj <nagaraj.sf@yahoo.com>
` Re: Single column vs composite partial index
  2020-09-18 20:54 UTC  Michael Lewis <mlewis@entrata.com>
  [4+ messages in thread]

autoanalyze creates bad plan, manual analyze fixes it?
  2020-09-14 23:11 UTC  Robert Treat <rob@xzilla.net>
` Re: autoanalyze creates bad plan, manual analyze fixes it?
  2020-09-14 23:41 UTC  Justin Pryzby <pryzby@telsasoft.com>
` Re: autoanalyze creates bad plan, manual analyze fixes it?
  2020-09-15 04:53 UTC  Pavel Stehule <pavel.stehule@gmail.com>
` Re: autoanalyze creates bad plan, manual analyze fixes it?
  2020-09-15 05:21 UTC  Robert Treat <rob@xzilla.net>
  [4+ messages in thread]

Performance Issue (Not using Index when joining two tables).
  2020-09-13 14:58 UTC  Gopisetty, Ramesh <rameshg2@illinois.edu>
` Re: Performance Issue (Not using Index when joining two tables).
  2020-09-13 16:47 UTC  Tomas Vondra <tomas.vondra@2ndquadrant.com>
` Re: Performance Issue (Not using Index when joining two tables).
  2020-09-13 17:07 UTC  Tom Lane <tgl@sss.pgh.pa.us>
` Re: Performance Issue (Not using Index when joining two tables).
  2020-09-14 02:51 UTC  Michael Lewis <mlewis@entrata.com>
` Re: Performance Issue (Not using Index when joining two tables).
  2020-09-14 03:18 UTC  Gopisetty, Ramesh <rameshg2@illinois.edu>
` Re: Performance Issue (Not using Index when joining two tables).
  2020-09-14 17:40 UTC  Tom Lane <tgl@sss.pgh.pa.us>
  [6+ messages in thread]

CPU hogged by concurrent SELECT..FOR UPDATE SKIP LOCKED
  2020-08-18 23:52 UTC  Jim Jarvie <jim@talentstack.to>
` Re: CPU hogged by concurrent SELECT..FOR UPDATE SKIP LOCKED
  2020-08-19 00:08 UTC  Michael Lewis <mlewis@entrata.com>
` Re: CPU hogged by concurrent SELECT..FOR UPDATE SKIP LOCKED
  2020-08-19 00:21 UTC  Jim Jarvie <jim@talentstack.to>
` Re: CPU hogged by concurrent SELECT..FOR UPDATE SKIP LOCKED
  2020-08-19 00:38 UTC  Henrique Montenegro <typoon@gmail.com>
` Re: CPU hogged by concurrent SELECT..FOR UPDATE SKIP LOCKED
  2020-08-19 00:39 UTC  Michael Lewis <mlewis@entrata.com>
` Re: CPU hogged by concurrent SELECT..FOR UPDATE SKIP LOCKED
  2020-08-19 00:45 UTC  Michael Lewis <mlewis@entrata.com>
` Re: CPU hogged by concurrent SELECT..FOR UPDATE SKIP LOCKED
  2020-08-19 06:04 UTC  Laurenz Albe <laurenz.albe@cybertec.at>
` Re: CPU hogged by concurrent SELECT..FOR UPDATE SKIP LOCKED
  2020-08-20 13:35 UTC  Jim Jarvie <jim@talentstack.to>
` Re: CPU hogged by concurrent SELECT..FOR UPDATE SKIP LOCKED
  2020-08-20 17:30 UTC  Michael Lewis <mlewis@entrata.com>
` Re: CPU hogged by concurrent SELECT..FOR UPDATE SKIP LOCKED
  2020-08-20 21:13 UTC  Jim Jarvie <jim@talentstack.to>
` Re: CPU hogged by concurrent SELECT..FOR UPDATE SKIP LOCKED
  2020-08-20 21:42 UTC  Michael Lewis <mlewis@entrata.com>
` Re: CPU hogged by concurrent SELECT..FOR UPDATE SKIP LOCKED
  2020-08-20 22:39 UTC  Jim Jarvie <jim@talentstack.to>
` Re: CPU hogged by concurrent SELECT..FOR UPDATE SKIP LOCKED
  2020-08-20 23:01 UTC  Michael Lewis <mlewis@entrata.com>
` Re: CPU hogged by concurrent SELECT..FOR UPDATE SKIP LOCKED
  2020-08-20 23:37 UTC  David Rowley <dgrowleyml@gmail.com>
` Re: CPU hogged by concurrent SELECT..FOR UPDATE SKIP LOCKED
  2020-08-21 04:34 UTC  Thomas Munro <thomas.munro@gmail.com>
` Re: CPU hogged by concurrent SELECT..FOR UPDATE SKIP LOCKED
  2020-08-21 15:24 UTC  Jim Jarvie <jim@talentstack.to>
` Re: CPU hogged by concurrent SELECT..FOR UPDATE SKIP LOCKED
  2020-08-24 17:58 UTC  Jeff Janes <jeff.janes@gmail.com>
` Re: CPU hogged by concurrent SELECT..FOR UPDATE SKIP LOCKED
  2020-09-07 18:04 UTC  Raj <raj@gusw.net>
` Re: CPU hogged by concurrent SELECT..FOR UPDATE SKIP LOCKED
  2020-09-11 18:29 UTC  Jim Jarvie <jim@talentstack.to>
` Re: CPU hogged by concurrent SELECT..FOR UPDATE SKIP LOCKED
  2020-09-13 13:52 UTC  David Rowley <dgrowleyml@gmail.com>
` Re: CPU hogged by concurrent SELECT..FOR UPDATE SKIP LOCKED
  2020-09-13 14:55 UTC  Alvaro Herrera <alvherre@2ndquadrant.com>
  [21+ messages in thread]

Query Performance in bundled requests
  2020-09-08 10:30 UTC  Dirk Krautschick <Dirk.Krautschick@trivadis.com>
` Re: Query Performance in bundled requests
  2020-09-08 10:49 UTC  Justin Pryzby <pryzby@telsasoft.com>
  [2+ messages in thread]

AW: Query performance issue
  2020-09-08 10:29 UTC  Dirk Krautschick <Dirk.Krautschick@trivadis.com>

Too few rows expected by Planner on partitioned tables
  2020-07-21 13:09 UTC  Julian Wolf <julian.wolf@invenium.io>
` Re: Too few rows expected by Planner on partitioned tables
  2020-07-21 17:27 UTC  Justin Pryzby <pryzby@telsasoft.com>
` Re: Too few rows expected by Planner on partitioned tables
  2020-07-22 06:33 UTC  Julian Wolf <julian.wolf@invenium.io>
` Re: Too few rows expected by Planner on partitioned tables
  2020-07-22 12:28 UTC  Justin Pryzby <pryzby@telsasoft.com>
` Re: Too few rows expected by Planner on partitioned tables
  2020-07-22 14:40 UTC  Justin Pryzby <pryzby@telsasoft.com>
` Re: Too few rows expected by Planner on partitioned tables
  2020-07-29 06:17 UTC  Julian Wolf <julian.wolf@invenium.io>
` Re: Too few rows expected by Planner on partitioned tables
  2020-08-26 06:54 UTC  Julian Wolf <julian.wolf@invenium.io>
` Re: Too few rows expected by Planner on partitioned tables
  2020-08-26 13:32 UTC  Michael Lewis <mlewis@entrata.com>
  [8+ messages in thread]

sizing / capacity planning tipps related to expected request or transactions per second
  2020-08-24 16:39 UTC  Dirk Krautschick <Dirk.Krautschick@trivadis.com>
` Re: sizing / capacity planning tipps related to expected request or transactions per second
  2020-08-24 16:49 UTC  MichaelDBA <MichaelDBA@sqlexec.com>
` Re: sizing / capacity planning tipps related to expected request or transactions per second
  2020-08-24 16:51 UTC  Pavel Stehule <pavel.stehule@gmail.com>
  [3+ messages in thread]

Query takes way longer with LIMIT, and EXPLAIN takes way longer than actual query
  2020-08-14 21:34 UTC  Ken Tanzer <ken.tanzer@gmail.com>
` Re: Query takes way longer with LIMIT, and EXPLAIN takes way longer than actual query
  2020-08-14 22:04 UTC  Justin Pryzby <pryzby@telsasoft.com>
` Re: Query takes way longer with LIMIT, and EXPLAIN takes way longer than actual query
  2020-08-14 22:40 UTC  Ken Tanzer <ken.tanzer@gmail.com>
` Re: Query takes way longer with LIMIT, and EXPLAIN takes way longer than actual query
  2020-08-15 00:24 UTC  Jeff Janes <jeff.janes@gmail.com>
` Re: Query takes way longer with LIMIT, and EXPLAIN takes way longer than actual query
  2020-08-15 00:55 UTC  Justin Pryzby <pryzby@telsasoft.com>
  [5+ messages in thread]

Hstore index for full text search
  2020-08-11 20:52 UTC  Burhan Akbulut <burhan.akbulut@cooksoft.com.tr>
` Re: Hstore index for full text search
  2020-08-11 21:55 UTC  Michael Lewis <mlewis@entrata.com>
` Re: Hstore index for full text search
  2020-08-11 22:46 UTC  Tom Lane <tgl@sss.pgh.pa.us>
` Re: Hstore index for full text search
  2020-08-11 22:57 UTC  Michael Lewis <mlewis@entrata.com>
` Re: Hstore index for full text search
  2020-08-11 23:30 UTC  Tom Lane <tgl@sss.pgh.pa.us>
  [5+ messages in thread]

Problems with Multixacts LWLocks
  2020-07-29 14:18 UTC  Czarek <keracz@protonmail.com>

Same query taking less time in low configuration machine
  2020-07-16 15:43 UTC  Vishwa Kalyankar <vishwakalyankar8@gmail.com>
` Re: Same query taking less time in low configuration machine
  2020-07-16 16:04 UTC  Justin Pryzby <pryzby@telsasoft.com>
` Re: Same query taking less time in low configuration machine
  2020-07-16 16:51 UTC  Vishwa Kalyankar <vishwakalyankar8@gmail.com>
` Re: Same query taking less time in low configuration machine
  2020-07-16 17:03 UTC  Justin Pryzby <pryzby@telsasoft.com>
` Re: Same query taking less time in low configuration machine
  2020-07-17 07:59 UTC  Vishwa Kalyankar <vishwakalyankar8@gmail.com>
  [5+ messages in thread]

Sudden insert performance degradation
  2020-07-13 14:23 UTC  Henrique Montenegro <typoon@gmail.com>
` Re: Sudden insert performance degradation
  2020-07-13 15:20 UTC  Sebastian Dressler <sebastian@swarm64.com>
` Re: Sudden insert performance degradation
  2020-07-13 16:27 UTC  Michael Lewis <mlewis@entrata.com>
` Re: Sudden insert performance degradation
  2020-07-13 16:42 UTC  Henrique Montenegro <typoon@gmail.com>
` Re: Sudden insert performance degradation
  2020-07-13 16:48 UTC  Henrique Montenegro <typoon@gmail.com>
` Re: Sudden insert performance degradation
  2020-07-13 16:50 UTC  Sebastian Dressler <sebastian@swarm64.com>
` Re: Sudden insert performance degradation
  2020-07-13 17:02 UTC  Henrique Montenegro <typoon@gmail.com>
` Re: Sudden insert performance degradation
  2020-07-14 00:05 UTC  Jeff Janes <jeff.janes@gmail.com>
` Re: Sudden insert performance degradation
  2020-07-14 01:02 UTC  Henrique Montenegro <typoon@gmail.com>
` Re: Sudden insert performance degradation
  2020-07-14 13:05 UTC  Henrique Montenegro <typoon@gmail.com>
` Re: Sudden insert performance degradation
  2020-07-15 01:13 UTC  Henrique Montenegro <typoon@gmail.com>
` Re: Sudden insert performance degradation
  2020-07-15 08:03 UTC  Sebastian Dressler <sebastian@swarm64.com>
` Re: Sudden insert performance degradation
  2020-07-15 12:24 UTC  Henrique Montenegro <typoon@gmail.com>
` Re: Sudden insert performance degradation
  2020-07-15 18:49 UTC  Henrique Montenegro <typoon@gmail.com>
` Re: Sudden insert performance degradation
  2020-07-15 20:03 UTC  Justin Pryzby <pryzby@telsasoft.com>
  [15+ messages in thread]

Request to help on Query improvement suggestion.
  2020-05-22 10:45 UTC  devchef2020 d <devchef2020@gmail.com>
` Re: Request to help on Query improvement suggestion.
  2020-05-25 06:47 UTC  Laurenz Albe <laurenz.albe@cybertec.at>
` Re: Request to help on Query improvement suggestion.
  2020-07-11 17:15 UTC  Marlene Villanueva <villanuevamarlene906@gmail.com>
  [3+ messages in thread]

Recommended value for pg_test_fsync
  2020-06-29 09:26 UTC  Nikhil Shetty <nikhil.dba04@gmail.com>
` Re: Recommended value for pg_test_fsync
  2020-06-29 16:06 UTC  Bruce Momjian <bruce@momjian.us>
` Re: Recommended value for pg_test_fsync
  2020-06-30 05:02 UTC  Nikhil Shetty <nikhil.dba04@gmail.com>
` Re: Recommended value for pg_test_fsync
  2020-06-30 15:24 UTC  Bruce Momjian <bruce@momjian.us>
` Re: Recommended value for pg_test_fsync
  2020-06-30 16:21 UTC  Jeff Janes <jeff.janes@gmail.com>
` Re: Recommended value for pg_test_fsync
  2020-06-30 17:26 UTC  Jeff Janes <jeff.janes@gmail.com>
` Re: Recommended value for pg_test_fsync
  2020-07-01 16:55 UTC  Nikhil Shetty <nikhil.dba04@gmail.com>
` Re: Recommended value for pg_test_fsync
  2020-07-01 17:06 UTC  Nikhil Shetty <nikhil.dba04@gmail.com>
` Re: Recommended value for pg_test_fsync
  2020-07-01 17:13 UTC  Nikhil Shetty <nikhil.dba04@gmail.com>
` Re: Recommended value for pg_test_fsync
  2020-07-01 17:16 UTC  Haroldo Kerry <hkerry@callix.com.br>
` Re: Recommended value for pg_test_fsync
  2020-07-01 17:43 UTC  Nikhil Shetty <nikhil.dba04@gmail.com>
` Re: Recommended value for pg_test_fsync
  2020-07-01 18:11 UTC  Nikhil Shetty <nikhil.dba04@gmail.com>
` Re: Recommended value for pg_test_fsync
  2020-07-01 19:59 UTC  Bruce Momjian <bruce@momjian.us>
  [13+ messages in thread]

PostgreSQL 12.3 slow index scan chosen
  2020-06-19 19:49 UTC  Kenneth Marshall <ktm@rice.edu>
` Re: PostgreSQL 12.3 slow index scan chosen
  2020-06-19 20:11 UTC  Tom Lane <tgl@sss.pgh.pa.us>
` Re: PostgreSQL 12.3 slow index scan chosen
  2020-06-19 20:49 UTC  Kenneth Marshall <ktm@rice.edu>
` Re: PostgreSQL 12.3 slow index scan chosen
  2020-06-19 20:59 UTC  Tom Lane <tgl@sss.pgh.pa.us>
` Re: PostgreSQL 12.3 slow index scan chosen
  2020-06-19 21:23 UTC  Kenneth Marshall <ktm@rice.edu>
` Re: PostgreSQL 12.3 slow index scan chosen
  2020-06-19 22:10 UTC  Tom Lane <tgl@sss.pgh.pa.us>
` Re: PostgreSQL 12.3 slow index scan chosen
  2020-06-19 22:25 UTC  Kenneth Marshall <ktm@rice.edu>
` Re: PostgreSQL 12.3 slow index scan chosen
  2020-06-19 22:30 UTC  Tom Lane <tgl@sss.pgh.pa.us>
` Re: PostgreSQL 12.3 slow index scan chosen
  2020-06-19 22:37 UTC  Kenneth Marshall <ktm@rice.edu>
` Re: PostgreSQL 12.3 slow index scan chosen
  2020-06-19 23:07 UTC  Tom Lane <tgl@sss.pgh.pa.us>
` Re: PostgreSQL 12.3 slow index scan chosen
  2020-06-20 18:22 UTC  Tom Lane <tgl@sss.pgh.pa.us>
` Re: PostgreSQL 12.3 slow index scan chosen
  2020-06-20 19:55 UTC  Kenneth Marshall <ktm@rice.edu>
` Re: PostgreSQL 12.3 slow index scan chosen
  2020-06-22 19:27 UTC  Alvaro Herrera <alvherre@2ndquadrant.com>
` Re: PostgreSQL 12.3 slow index scan chosen
  2020-06-22 19:29 UTC  Kenneth Marshall <ktm@rice.edu>
` Re: PostgreSQL 12.3 slow index scan chosen
  2020-06-22 19:39 UTC  Tom Lane <tgl@sss.pgh.pa.us>
  [15+ messages in thread]

Unclamped row estimates whith OR-ed subplans
  2020-06-19 15:12 UTC  Benjamin Coutu <ben.coutu@zeyos.com>
` Re: Unclamped row estimates whith OR-ed subplans
  2020-06-19 15:55 UTC  Laurenz Albe <laurenz.albe@cybertec.at>
` Re: Unclamped row estimates whith OR-ed subplans
  2020-06-19 16:04 UTC  Tom Lane <tgl@sss.pgh.pa.us>
` Re: Unclamped row estimates whith OR-ed subplans
  2020-06-19 16:14 UTC  David G. Johnston <david.g.johnston@gmail.com>
` Re: Unclamped row estimates whith OR-ed subplans
  2020-06-19 17:33 UTC  Benjamin Coutu <ben.coutu@zeyos.com>
` Re: Unclamped row estimates whith OR-ed subplans
  2020-06-19 18:16 UTC  Tom Lane <tgl@sss.pgh.pa.us>
` Re: Unclamped row estimates whith OR-ed subplans
  2020-06-19 18:37 UTC  Michael Lewis <mlewis@entrata.com>
` Re: Unclamped row estimates whith OR-ed subplans
  2020-06-19 20:33 UTC  Benjamin Coutu <ben.coutu@zeyos.com>
  [8+ messages in thread]

simple query running for ever
  2020-06-16 20:35 UTC  Nagaraj Raj <nagaraj.sf@yahoo.com>
` Re: simple query running for ever
  2020-06-16 20:43 UTC  Michael Lewis <mlewis@entrata.com>
` Re: simple query running for ever
  2020-06-16 20:46 UTC  Justin Pryzby <pryzby@telsasoft.com>
` Re: simple query running for ever
  2020-06-16 20:57 UTC  Nagaraj Raj <nagaraj.sf@yahoo.com>
` Re: simple query running for ever
  2020-06-16 21:13 UTC  Nagaraj Raj <nagaraj.sf@yahoo.com>
` Re: simple query running for ever
  2020-06-16 21:15 UTC  Nagaraj Raj <nagaraj.sf@yahoo.com>
` Re: simple query running for ever
  2020-06-16 22:05 UTC  Justin Pryzby <pryzby@telsasoft.com>
` Re: simple query running for ever
  2020-06-16 22:10 UTC  Andreas Joseph Krogh <andreas@visena.com>
` Re: simple query running for ever
  2020-06-16 22:33 UTC  Justin Pryzby <pryzby@telsasoft.com>
` Re: simple query running for ever
  2020-06-17 09:23 UTC  Laurenz Albe <laurenz.albe@cybertec.at>
  [10+ messages in thread]

view reading information_schema is slow in PostgreSQL 12
  2020-06-12 15:21 UTC  regrog <andrea.vencato@gmail.com>
` Re: view reading information_schema is slow in PostgreSQL 12
  2020-06-12 19:00 UTC  Imre Samu <pella.samu@gmail.com>
` Re: view reading information_schema is slow in PostgreSQL 12
  2020-06-13 03:11 UTC  Tom Lane <tgl@sss.pgh.pa.us>
` Re: view reading information_schema is slow in PostgreSQL 12
  2020-06-13 03:15 UTC  David Rowley <dgrowleyml@gmail.com>
` Re: view reading information_schema is slow in PostgreSQL 12
  2020-06-13 03:55 UTC  David Rowley <dgrowleyml@gmail.com>
` Re: view reading information_schema is slow in PostgreSQL 12
  2020-06-13 04:07 UTC  Tom Lane <tgl@sss.pgh.pa.us>
` Re: view reading information_schema is slow in PostgreSQL 12
  2020-06-13 04:34 UTC  Justin Pryzby <pryzby@telsasoft.com>
` Re: view reading information_schema is slow in PostgreSQL 12
  2020-06-13 05:13 UTC  Pavel Stehule <pavel.stehule@gmail.com>
` Re: view reading information_schema is slow in PostgreSQL 12
  2020-06-13 05:15 UTC  Pavel Stehule <pavel.stehule@gmail.com>
` Re: view reading information_schema is slow in PostgreSQL 12
  2020-06-13 05:23 UTC  Pavel Stehule <pavel.stehule@gmail.com>
` Re: view reading information_schema is slow in PostgreSQL 12
  2020-06-13 07:52 UTC  David Rowley <dgrowleyml@gmail.com>
` Re: view reading information_schema is slow in PostgreSQL 12
  2020-06-13 08:22 UTC  David Rowley <dgrowleyml@gmail.com>
` Re: view reading information_schema is slow in PostgreSQL 12
  2020-06-13 17:06 UTC  Tom Lane <tgl@sss.pgh.pa.us>
` Re: view reading information_schema is slow in PostgreSQL 12
  2020-06-15 18:21 UTC  Michael Lewis <mlewis@entrata.com>
` Re: view reading information_schema is slow in PostgreSQL 12
  2020-06-16 09:23 UTC  regrog <andrea.vencato@gmail.com>
  [15+ messages in thread]

Performance issue
  2003-09-24 05:48 UTC  peter <pmcgregor@advso.com>
` Re: Performance issue
  2003-09-24 17:05 UTC  Richard Jones <rj@last.fm>
` Re: Performance issue
  2003-09-24 17:09 UTC  Joseph Bove <jbove@vetstar.com>
` Re: Performance issue
  2003-09-24 17:47 UTC  Sean Chittenden <sean@chittenden.org>
` Re: Performance issue
  2003-09-24 18:35 UTC  Rod Taylor <rbt@rbt.ca>
` Performance issue
  2007-08-27 12:16 UTC  Willo van der Merwe <willo@studentvillage.co.za>
` Performance issue
  2007-08-27 13:41 UTC  Willo van der Merwe <willo@mirasol.co.za>
` Re: Performance issue
  2007-08-27 14:45 UTC  Bill Moran <wmoran@collaborativefusion.com>
` Re: Performance issue
  2007-08-27 15:55 UTC  Tom Lane <tgl@sss.pgh.pa.us>
` Re: Performance issue
  2007-08-28 09:34 UTC  Willo van der Merwe <willo@mirasol.co.za>
` Performance issue
  2020-06-14 22:45 UTC  Nagaraj Raj <nagaraj.sf@yahoo.com>
` Re: Performance issue
  2020-06-14 23:55 UTC  David Rowley <dgrowleyml@gmail.com>
` Re: Performance issue
  2020-06-15 00:05 UTC  Justin Pryzby <pryzby@telsasoft.com>
  [13+ messages in thread]

Windows slowness?
  2020-06-10 19:28 UTC  Mikkel Lauritsen <renard@tala.dk>
` Re: Windows slowness?
  2020-06-10 20:35 UTC  mountain the blue <thebluemountain@gmail.com>
` Re: Windows slowness?
  2020-06-10 21:08 UTC  David Rowley <dgrowleyml@gmail.com>
` Re: Windows slowness?
  2020-06-11 05:05 UTC  Mikkel Lauritsen <renard@tala.dk>
  [4+ 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