Re: Very slow updates when using IN syntax subselect

From: Bryce Nesbitt <bryce1(at)obviously(dot)com>
To: pgsql-sql(at)postgresql(dot)org
Subject: Re: Very slow updates when using IN syntax subselect
Date: 2006-02-11 19:48:07
Message-ID: 43EE3F77.6020108@obviously.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-sql

Tom Lane wrote:
> Bryce Nesbitt <bryce1(at)obviously(dot)com> writes:
>
>> Tom Lane wrote:
>>
>>> What does EXPLAIN show for this and for the base query?
>>>
>
>
>> -> Seq Scan on event (cost=0.00..0.00 rows=1 width=408)
>> Filter: (reconciled = false)
>>
>
>
>> select count(*) from event;
>> -----------
>> 116226
>>
>
> It seems pretty clear that you've never vacuumed nor analyzed these
> tables ... else the planner would have some clue about their sizes.
> Do that and then see what you get.
>
They occur in fine time. That's good, thanks. But jeeze, can't
postgres figure this out for itself?

In response to

Responses

Browse pgsql-sql by date

  From Date Subject
Next Message Peter Eisentraut 2006-02-11 20:34:57 Re: Very slow updates when using IN syntax subselect
Previous Message Tom Lane 2006-02-11 15:47:42 Re: Very slow updates when using IN syntax subselect