Re: Weird issue with planner choosing seq scan

From: "Scott Marlowe" <scott(dot)marlowe(at)gmail(dot)com>
To: "Sean Leach" <sleach(at)wiggum(dot)com>
Cc: "Stephen Denne" <Stephen(dot)Denne(at)datamail(dot)co(dot)nz>, pgsql-performance <pgsql-performance(at)postgresql(dot)org>
Subject: Re: Weird issue with planner choosing seq scan
Date: 2008-02-25 00:27:55
Message-ID: dcc563d10802241627g6d30808erf1006b3ffe6e1d08@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-performance

On Sun, Feb 24, 2008 at 6:05 PM, Sean Leach <sleach(at)wiggum(dot)com> wrote:

> On Feb 24, 2008, at 4:03 PM, Scott Marlowe wrote:
>
> >
> > What version pgsql is this? If it's pre 8.0 it might be worth looking
> > into migrating for performance and maintenance reasons.
>
> It's the latest 8.3.0 release :(

Urg. Then I wonder how your indexes are bloating but your table is
not... you got autovac running? No weird lock issues? It's a side
issue right now since the table is showing as non-bloated (unless
you've got a long running transaction and that number is WAY off from
your vacuum)

In response to

Responses

Browse pgsql-performance by date

  From Date Subject
Next Message Joel Stevenson 2008-02-25 07:09:30 Re: LISTEN / NOTIFY performance in 8.3
Previous Message Sean Leach 2008-02-25 00:05:18 Re: Weird issue with planner choosing seq scan