Mailing lists [pgsql-performance]

2 February 2020

• 17:18   Statistics on array values Marco Colli
• 17:23   Re: Statistics on array values Justin Pryzby
• 17:38   Re: Statistics on array values Marco Colli
• 20:11   Re: Statistics on array values Tom Lane
• 21:26   Re: Statistics on array values Marco Colli
• 21:32   Re: Statistics on array values Tom Lane
• 21:55   Re: Statistics on array values Marco Colli

3 February 2020

• 23:38   Slow performance with trivial self-joins Benny Kramek

4 February 2020

• 00:10   Re: Slow performance with trivial self-joins Tom Lane

5 February 2020

• 20:03   Writing 1100 rows per second Arya F
• 20:12   Re: Writing 1100 rows per second Laurenz Albe
• 20:15   Re: Writing 1100 rows per second Justin Pryzby
• 20:25   Re: Writing 1100 rows per second Arya F
• 20:46   Re: Writing 1100 rows per second Haroldo Kerry

6 February 2020

• 00:55   Re: Slow performance with trivial self-joins Benny Kramek
• 01:12   Re: Slow performance with trivial self-joins Adam Brusselback
• 02:47   Re: Slow performance with trivial self-joins David Rowley
• 21:15   Re: Writing 1100 rows per second Ogden Brash

7 February 2020

• 16:07   TOAST table performance problem Asya Nevra Buyuksoy
• 16:12   Sv: TOAST table performance problem Andreas Joseph Krogh
• 16:23   Re: TOAST table performance problem Asya Nevra Buyuksoy
• 16:34   Re: TOAST table performance problem Asya Nevra Buyuksoy
• 16:41   Re: TOAST table performance problem Andreas Joseph Krogh
• 16:52   Re: TOAST table performance problem MichaelDBA
• 17:16   Re: TOAST table performance problem Asya Nevra Buyuksoy
• 17:19   Re: TOAST table performance problem Andreas Joseph Krogh
• 17:42   Re: TOAST table performance problem Andreas Joseph Krogh
• 17:59   Re: TOAST table performance problem Asya Nevra Buyuksoy
• 18:15   Re: TOAST table performance problem Andreas Joseph Krogh

9 February 2020

• 22:30   Re: Writing 1100 rows per second Jeff Janes

10 February 2020

• 10:52   Fwd: TOAST table performance problem Asya Nevra Buyuksoy
• 13:34   Bad selectivity estimate when using a sub query to determine WHERE condition Chris Borckholder
• 15:31   Re: Fwd: TOAST table performance problem Luís Roberto Weck
• 15:38   Re: Fwd: TOAST table performance problem Asya Nevra Buyuksoy
• 15:53   Re: Fwd: TOAST table performance problem Jeff Janes
• 15:59   Re: Fwd: TOAST table performance problem Asya Nevra Buyuksoy
• 18:39   Re: Bad selectivity estimate when using a sub query to determine WHERE condition Tom Lane
• 22:13   Re: Bad selectivity estimate when using a sub query to determineWHERE condition Justin Pryzby

12 February 2020

• 08:28   Re: Writing 1100 rows per second Amol Tarte
• 11:09   Re: Bad selectivity estimate when using a sub query to determineWHERE condition Chris Borckholder
• 11:12   Re: Bad selectivity estimate when using a sub query to determineWHERE condition Chris Borckholder

13 February 2020

• 13:21   How to avoid UPDATE performance degradation in a transaction Karl Düüna
• 23:50   Re: How to avoid UPDATE performance degradation in a transaction David G. Johnston

14 February 2020

• 00:16   Re: How to avoid UPDATE performance degradation in a transaction Tom Lane
• 10:14   Re: How to avoid UPDATE performance degradation in a transaction Karl Düüna
• 20:54   Re: How to avoid UPDATE performance degradation in a transaction Michael Lewis

15 February 2020

• 14:04   Partial index creation always scans the entire table MingJu Wu
• 15:47   Re: Partial index creation always scans the entire table Sergei Kornilov
• 15:53   Re: Partial index creation always scans the entire table Justin Pryzby

16 February 2020

• 00:15   Re: Partial index creation always scans the entire table Laurenz Albe
• 18:30   Re: Partial index creation always scans the entire table Tom Lane
• 18:59   Re: Partial index creation always scans the entire table Justin Pryzby
• 19:35   Re: Partial index creation always scans the entire table Tom Lane
• 20:15   SubtransControlLock and performance problems Lars Aksel Opsahl

17 February 2020

• 03:43   RE: Partial index creation always scans the entire table Mike Sofen
• 03:52   Re: Partial index creation always scans the entire table Justin Pryzby
• 04:09   Re: Partial index creation always scans the entire table Tom Lane
• 12:53   Re: SubtransControlLock and performance problems Laurenz Albe
• 18:03   Re: SubtransControlLock and performance problems Lars Aksel Opsahl
• 19:35   Re: SubtransControlLock and performance problems Laurenz Albe
• 21:01   Re: SubtransControlLock and performance problems Pavel Stehule
• 21:23   Re: SubtransControlLock and performance problems Tom Lane
• 21:41   Re: SubtransControlLock and performance problems Pavel Stehule
• 22:10   Re: SubtransControlLock and performance problems Alvaro Herrera

18 February 2020

• 20:27   Re: SubtransControlLock and performance problems Laurenz Albe
• 21:40   Re: DB running out of memory issues after upgrade Justin Pryzby
• 21:49   Re: DB running out of memory issues after upgrade Merlin Moncure
• 22:10   Re: DB running out of memory issues after upgrade Nagaraj Raj

19 February 2020

• 02:46   Re: SubtransControlLock and performance problems Pavel Stehule
• 07:42   tablespace to benefit from ssd ? Nicolas PARIS
• 11:02   Re: tablespace to benefit from ssd ? Sebastiaan Mannem
• 13:48   Re: tablespace to benefit from ssd ? Laurenz Albe
• 13:49   Re: SubtransControlLock and performance problems Lars Aksel Opsahl
• 16:08   Re: tablespace to benefit from ssd ? Justin Pryzby
• 18:23   Re: SubtransControlLock and performance problems Alvaro Herrera

20 February 2020

• 07:35   Re: How to avoid UPDATE performance degradation in a transaction Andres Freund
• 12:20   Re: SubtransControlLock and performance problems Lars Aksel Opsahl
• 20:30   Re: tablespace to benefit from ssd ? Jeff Janes

21 February 2020

• 19:24   RE: Can we have multiple tablespaces with in a database. Patrick FICHE

22 February 2020

• 07:45   RE: Can we have multiple tablespaces with in a database. Daulat Ram

23 February 2020

• 12:56   PostgreSQL 11 higher Planning time on Partitioned table Ravi Garg
• 13:12   Re: PostgreSQL 11 higher Planning time on Partitioned table Justin Pryzby
• 13:46   Re: PostgreSQL 11 higher Planning time on Partitioned table Justin Pryzby
• 13:57   Re: PostgreSQL 11 higher Planning time on Partitioned table Ravi Garg
• 18:10   Re: PostgreSQL 11 higher Planning time on Partitioned table Justin Pryzby
• 19:18   Re: PostgreSQL 11 higher Planning time on Partitioned table Imre Samu

24 February 2020

• 19:34   Re: DB running out of memory issues after upgrade Merlin Moncure
• 22:40   Re: PostgreSQL 11 higher Planning time on Partitioned table Ravi Garg
• 22:44   Re: PostgreSQL 11 higher Planning time on Partitioned table Ravi Garg

26 February 2020

• 19:17   much slower query in production Guillaume Cottenceau
• 19:28   Re: much slower query in production Justin Pryzby
• 19:52   Re: much slower query in production Michael Lewis
• 21:02   Re: much slower query in production Guillaume Cottenceau
• 21:04   Re: much slower query in production Guillaume Cottenceau
• 21:18   Re: much slower query in production Michael Lewis
• 22:18   Re: much slower query in production MichaelDBA@sqlexec.com
• 22:37   Re: much slower query in production Guillaume Cottenceau

27 February 2020

• 01:59   Re: much slower query in production Jeff Janes
• 02:17   Re: much slower query in production Jeff Janes
• 11:31   Re: much slower query in production Guillaume Cottenceau
• 19:33   Many DataFileRead - IO waits Ben Snaidero
• 19:54   Re: Many DataFileRead - IO waits Michael Lewis

28 February 2020

• 17:01   Re: Many DataFileRead - IO waits Ben Snaidero
• 19:40   Re: Many DataFileRead - IO waits Michael Lewis
• 19:53   Re: Many DataFileRead - IO waits Ben Snaidero
• 22:00   Re: Many DataFileRead - IO waits legrand legrand

29 February 2020

• 19:21   Re: Many DataFileRead - IO waits Jeff Janes