Home > mailing lists

Mailing lists [pgsql-performance]

1 May 2015

13:54 Index Scan Backward Slow David Osborne
13:59 Re: Index Scan Backward Slow Evgeniy Shishkin
14:06 Re: Index Scan Backward Slow David Osborne

2 May 2015

11:49 Re: Index Scan Backward Slow Robert Klemme

4 May 2015

00:23 optimization join on random value Anton Bushmelev
00:28 Re: optimization join on random value Heikki Linnakangas

13 May 2015

04:08 How to clean/truncate / VACUUM FULL pg_largeobject without (much) downtime? Muthusamy, Sivaraman

21 May 2015

04:14 Re: Fastest way / best practice to calculate "next birthdays" er.tejaspatel88@gmail.com
06:22 Re: Fastest way / best practice to calculate "next birthdays" David G. Johnston
13:41 union all and filter / index scan -> seq scan Florian Lohoff
18:09 Re: union all and filter / index scan -> seq scan Vitalii Tymchyshyn
18:28 Re: union all and filter / index scan -> seq scan Tom Lane
19:15 Re: Fastest way / best practice to calculate "next birthdays" Bosco Rama
19:50 Re: Fastest way / best practice to calculate "next birthdays" David G. Johnston
21:54 Re: PostgreSQL disk fragmentation causes performance problems on Windows Josh Berkus
23:39 Re: PostgreSQL disk fragmentation causes performance problems on Windows Andres Freund

22 May 2015

02:16 Re: PostgreSQL disk fragmentation causes performance problems on Windows Vitalii Tymchyshyn
20:34 Re: PostgreSQL disk fragmentation causes performance problems on Windows Josh Berkus

23 May 2015

00:18 Re: How to clean/truncate / VACUUM FULL pg_largeobject without (much) downtime? Jim Nasby
00:23 Re: Fastest way / best practice to calculate "next birthdays" Jim Nasby
01:27 MAX() and multi-column index on a partitioned table? Dave Johansen
01:42 Re: MAX() and multi-column index on a partitioned table? Tom Lane
02:53 Re: MAX() and multi-column index on a partitioned table? Dave Johansen
04:16 Re: MAX() and multi-column index on a partitioned table? Tom Lane

27 May 2015

10:50 ERROR: missing chunk number 0 for toast value 1821556134 in pg_toast_17881 Tory M Blue
23:24 Fastest Backup & Restore for perf testing Wes Vaske (wvaske)
23:37 Re: Fastest Backup & Restore for perf testing Andrew Dunstan
23:39 Re: Fastest Backup & Restore for perf testing Steve Atkins

28 May 2015

01:02 Re: ERROR: missing chunk number 0 for toast value 1821556134 in pg_toast_17881 Josh Berkus
17:31 Partitioning and performance Ravi Krishna
17:41 Re: Partitioning and performance Ravi Krishna
20:40 Re: Fastest Backup & Restore for perf testing Jim Nasby
21:05 Re: Partitioning and performance Jim Nasby

29 May 2015

11:55 Different plan for very similar queries Peter J. Holzer
12:51 Re: Different plan for very similar queries Peter J. Holzer
20:57 Fwd: Postgres is using 100% CPU Ashik S L
21:10 Postgres is using 100% CPU Ashik S L
21:30 Re: Postgres is using 100% CPU Yves Dorfsman
22:20 Re: Postgres is using 100% CPU Tomas Vondra

30 May 2015

02:47 Re: Different plan for very similar queries Tomas Vondra
16:46 Re: Postgres is using 100% CPU Ashik S L
17:20 Re: Postgres is using 100% CPU Tomas Vondra
22:04 Re: Different plan for very similar queries Tom Lane
22:57 Postmaster eating up all my cpu birimblongas
23:45 Re: Postmaster eating up all my cpu Tomas Vondra

31 May 2015

14:00 Re: Different plan for very similar queries Peter J. Holzer
16:05 Re: Postgres is using 100% CPU Jean-David Beyer
17:23 Re: Postgres is using 100% CPU Yves Dorfsman
18:51 Re: Different plan for very similar queries Tom Lane
19:06 Re: Different plan for very similar queries Tomas Vondra
19:22 Re: Different plan for very similar queries Tom Lane
19:39 Re: Different plan for very similar queries Tomas Vondra