From: Bryce Nesbitt <bryce1@obviously.com>
To: pgsql-sql@postgresql.org
Subject: Re: Very slow updates when using IN syntax subselect
Date: Sat, 11 Feb 2006 11:48:07 -0800
Message-ID: <43EE3F77.6020108@obviously.com> (raw)
In-Reply-To: <7972.1139672862@sss.pgh.pa.us>
References: <43ECFF0B.80905@obviously.com>
<1682.1139607176@sss.pgh.pa.us>
<43ED723E.9080305@obviously.com>
<7972.1139672862@sss.pgh.pa.us>
Tom Lane wrote:
> Bryce Nesbitt <bryce1@obviously.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?
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-sql@postgresql.org
Cc: bryce1@obviously.com
Subject: Re: Very slow updates when using IN syntax subselect
In-Reply-To: <43EE3F77.6020108@obviously.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox