Mailing lists [pgsql-performance]

20 December 2012

• 00:13   Why does the query planner use two full indexes, when a dedicated partial index exists? Richard Neill
• 02:00   Re: Why does the query planner use two full indexes, when a dedicated partial index exists? Sergey Konoplev
• 02:49   Re: Why does the query planner use two full indexes, when a dedicated partial index exists? Richard Neill
• 03:09   Re: Why does the query planner use two full indexes, when a dedicated partial index exists? Sergey Konoplev
• 03:22   Re: Why does the query planner use two full indexes, when a dedicated partial index exists? Richard Neill
• 04:02   Re: hash join vs nested loop join Huan Ruan
• 06:06   Re: Why does the query planner use two full indexes, when a dedicated partial index exists? Tom Lane
• 08:12   Re: Why does the query planner use two full indexes, when a dedicated partial index exists? Jeff Janes
• 08:52   Re: Why does the query planner use two full indexes, when a dedicated partial index exists? Richard Neill
• 08:57   Re: Why does the query planner use two full indexes, when a dedicated partial index exists? Richard Neill
• 17:06   Re: hash join vs nested loop join Kevin Grittner
• 18:43   Re: Why does the query planner use two full indexes, when a dedicated partial index exists? Tom Lane
• 18:49   Re: Why does the query planner use two full indexes, when a dedicated partial index exists? Tom Lane
• 20:29   Performance on Bulk Insert to Partitioned Table Charles Gomes
• 20:39   Re: Performance on Bulk Insert to Partitioned Table Scott Marlowe
• 21:55   Re: Performance on Bulk Insert to Partitioned Table Charles Gomes
• 23:02   Re: Performance on Bulk Insert to Partitioned Table Stephen Frost
• 23:08   Re: Performance on Bulk Insert to Partitioned Table Charles Gomes