Mailing lists [pgsql-performance]

4 May 2017

• 16:52   [PERFORM] Inefficient max query when using group by 
• 19:21   Re: [PERFORM] Inefficient max query when using group by bricklen
• 19:51   Re: [PERFORM] Inefficient max query when using group by David Rowley
• 20:10   [PERFORM] Postgres performance issue Junaid Malik
• 20:36   Re: [PERFORM] Postgres performance issue Scott Marlowe
• 20:57   Re: [PERFORM] Postgres performance issue Scott Marlowe

8 May 2017

• 23:49   [PERFORM] Speed differences between two servers Vincent Veyron

9 May 2017

• 00:48   Re: [PERFORM] Speed differences between two servers Scott Marlowe
• 00:50   Re: [PERFORM] Postgres performance issue Scott Marlowe
• 02:23   [PERFORM] Postgres uses too much RAM Hans Braxmeier
• 04:24   Re: [PERFORM] Speed differences between two servers Vincent Veyron
• 05:06   Re: [PERFORM] Speed differences between two servers Scott Marlowe
• 05:12   Re: [PERFORM] Postgres uses too much RAM Merlin Moncure
• 05:35   Re: [PERFORM] Speed differences between two servers Scott Marlowe
• 18:02   Re: [PERFORM] Speed differences between two servers Vincent Veyron
• 19:08   Re: [PERFORM] Speed differences between two servers Vincent Veyron
• 22:24   Re: [PERFORM] Speed differences between two servers Scott Marlowe

10 May 2017

• 14:27   Re: [PERFORM] Speed differences between two servers Vincent Veyron

11 May 2017

• 19:54   [PERFORM] Speed differences between in executing the same query plukovic
• 20:06   Re: [PERFORM] Speed differences between in executing the same query Tom Lane
• 23:11   Re: [PERFORM] Speed differences between in executing the same query plukovic

16 May 2017

• 03:42   [PERFORM] postgres_fdw and column casting shippability Jeff Janes
• 04:22   Re: [PERFORM] postgres_fdw and column casting shippability Tom Lane
• 22:54   Re: [PERFORM] postgres_fdw and column casting shippability Jeff Janes

19 May 2017

• 21:14   [PERFORM] GIN index not used if created in the same transaction as query Adam Brusselback
• 21:33   Re: [PERFORM] GIN index not used if created in the same transaction as query Tom Lane
• 21:49   Re: [PERFORM] GIN index not used if created in the same transactionas query Adam Brusselback
• 22:09   Re: [PERFORM] GIN index not used if created in the same transaction as query Tom Lane

20 May 2017

• 05:04   [PERFORM] pg_stat_statements with fetch Jeff Janes

21 May 2017

• 05:33   [PERFORM] Index not being used on composite type for particular query Zac Goldstein
• 06:00   Re: [PERFORM] Index not being used on composite type for particular query Tom Lane
• 08:51   Re: [PERFORM] Index not being used on composite type for particular query Zac Goldstein
• 12:25   [PERFORM] Bulk persistence strategy Riaan Stander
• 19:53   Re: [PERFORM] pg_stat_statements with fetch Rick Otten
• 20:33   Re: [PERFORM] Bulk persistence strategy Tom Lane

22 May 2017

• 01:29   Re: [PERFORM] Bulk persistence strategy Riaan Stander
• 04:37   Re: [PERFORM] Bulk persistence strategy Tom Lane
• 08:14   Re: [PERFORM] Bulk persistence strategy Riaan Stander
• 11:15   Re: [PERFORM] Bulk persistence strategy Simon Riggs
• 14:06   Re: [PERFORM] Bulk persistence strategy Riaan Stander
• 14:27   Re: [PERFORM] Bulk persistence strategy Simon Riggs
• 15:36   Re: [PERFORM] Bulk persistence strategy Riaan Stander
• 17:50   Re: [PERFORM] Bulk persistence strategy Tom Lane
• 21:17   [PERFORM] index of only not null, use function index? Ariel
• 21:37   Re: [PERFORM] Bulk persistence strategy Merlin Moncure

23 May 2017

• 01:57   [PERFORM] select subquery versus join subquery Jeff Janes
• 02:21   [PERFORM] Can postgresql plan a query using multiple CPU cores? Clemens Eisserer
• 02:52   Re: [PERFORM] Can postgresql plan a query using multiple CPU cores? David G. Johnston
• 04:37   Re: [PERFORM] Can postgresql plan a query using multiple CPU cores? Mark Kirkwood
• 10:41   Re: [PERFORM] Can postgresql plan a query using multiple CPU cores? Pavel Stehule
• 17:03   Re: [PERFORM] select subquery versus join subquery Gunnar \"Nick\" Bluth
• 18:42   [PERFORM] Log update query along with username who has executed the same. Dinesh Chandra 12108
• 18:49   Re: [PERFORM] Log update query along with username who has executedthe same. Rick Otten
• 19:07   Re: [PERFORM] Log update query along with username who has executed thesame. Dinesh Chandra 12108
• 22:59   Re: [PERFORM] select subquery versus join subquery Jeff Janes

24 May 2017

• 00:29   [PERFORM] More cores or higer frequency ? Jarek
• 00:39   Re: [PERFORM] More cores or higer frequency ? Steve Crawford
• 02:14   Re: [PERFORM] More cores or higer frequency ? Jarek
• 02:49   Re: [PERFORM] More cores or higer frequency ? Sven R. Kunze
• 03:36   Re: [PERFORM] More cores or higer frequency ? Scott Marlowe
• 03:40   Re: [PERFORM] More cores or higer frequency ? Steve Crawford
• 12:41   Re: [PERFORM] select subquery versus join subquery Gunnar \"Nick\" Bluth
• 23:04   [PERFORM] Query is running very slow...... Dinesh Chandra 12108
• 23:25   Re: [PERFORM] Query is running very slow...... Tomas Vondra

25 May 2017

• 03:17   [PERFORM] join estimate of subqueries with range conditions and constraintexclusion Justin Pryzby
• 11:13   [PERFORM] Query is very much slow Daulat Ram
• 13:49   Re: [PERFORM] Query is very much slow Andreas Kretschmer
• 14:10   Re: [PERFORM] Query is very much slow Andreas Kretschmer
• 18:21   Re: [PERFORM] Delete, foreign key, index usage Johann Spies
• 18:26   FW: Re: [PERFORM] Query is running very slow...... Dinesh Chandra 12108
• 21:38   Re: FW: Re: [PERFORM] Query is running very slow...... Tomas Vondra

26 May 2017

• 00:29   [PERFORM] Multicolumn B-Tree index - order by on 1st column and IN lookup for 2nd Alexandru Lazarev
• 01:48   [PERFORM] Monitoring tool for Postgres Database Ravi Tammineni
• 02:00   Re: [PERFORM] [ADMIN] Monitoring tool for Postgres Database Scott Whitney
• 05:05   Re: [PERFORM] Monitoring tool for Postgres Database Gary Evans
• 07:20   Re: [PERFORM] [ADMIN] Monitoring tool for Postgres Database Steven Chang
• 08:15   Re: [PERFORM] [ADMIN] Monitoring tool for Postgres Database Scott Mead
• 16:19   Re: [PERFORM] Monitoring tool for Postgres Database Rick Otten
• 17:31   Re: [PERFORM] [ADMIN] Monitoring tool for Postgres Database Joshua D. Drake
• 18:31   Re: FW: Re: [PERFORM] Query is running very slow...... Dinesh Chandra 12108
• 19:10   Re: FW: Re: [PERFORM] Query is running very slow...... Andreas Kretschmer
• 20:02   [PERFORM] Client Server performance & UDS Kevin.Hughes@uk.fujitsu.com
• 20:14   Re: [PERFORM] [ADMIN] Monitoring tool for Postgres Database Tatsuo Ishii
• 20:28   Re: [PERFORM] [ADMIN] Monitoring tool for Postgres Database Ashish Tiwari
• 20:31   Re: [PERFORM] Monitoring tool for Postgres Database gevans
• 20:32   Re: [PERFORM] Monitoring tool for Postgres Database Sunkara, Amrutha
• 23:51   Re: [PERFORM] More cores or higer frequency ? ldh@laurent-hasson.com

27 May 2017

• 10:58   Re: [PERFORM] Monitoring tool for Postgres Database Dave Stibrany
• 14:40   [PERFORM] Different plan between 9.6 and 9.4 when using "Group by" 梁海安（Killua Leung）
• 18:26   Re: [PERFORM] Client Server performance & UDS Rick Otten
• 21:42   Re: [PERFORM] Monitoring tool for Postgres Database phb07

30 May 2017

• 00:21   Re: [PERFORM] Different plan between 9.6 and 9.4 when using "Group by" Jeff Janes
• 13:34   Re: [PERFORM] Client Server performance & UDS Kevin.Hughes@uk.fujitsu.com
• 16:17   Re: [PERFORM] Client Server performance & UDS Rick Otten
• 16:52   [PERFORM] Re: join estimate of subqueries with range conditions and constraintexclusion Justin Pryzby

31 May 2017

• 02:20   Re: [PERFORM] Client Server performance & UDS Karl Czajkowski