Postgres Pro
Downloads
Home   >   mailing lists

Re: optimizer behavior in the case of highly updated tables - Mailing list pgsql-admin

From Scott Marlowe
Subject Re: optimizer behavior in the case of highly updated tables
Date
Msg-id AANLkTik8XqRz6pheRvn3X52aRmTRqJnqagPrJJLEZFSy@mail.gmail.com
Whole thread Raw
In response to optimizer behavior in the case of highly updated tables  (Mark Rostron <mrostron@ql2.com>)
List pgsql-admin
Tree view 
On Tue, Jun 8, 2010 at 8:58 PM, Mark Rostron <mrostron@ql2.com> wrote:
> I am looking for some specific information regarding optimizer behavior.
>
> We recently experienced a situation where a query that was previously using
> a btree lookup (efficient) SWITCHED to using seqscan/hash lookup.

OK, before we go any further, got any explain analyze output of the
fast and slow queries?

pgsql-admin by date:

Previous
From: Greg Smith
Date:
Subject: Re: Details about pg_stat_bgwriter
Next
From: Scott Marlowe
Date:
Subject: Re: Details about pg_stat_bgwriter