Re: Very slow updates when using IN syntax subselect

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Bryce Nesbitt <bryce1(at)obviously(dot)com>
Cc: pgsql-sql(at)postgresql(dot)org
Subject: Re: Very slow updates when using IN syntax subselect
Date: 2006-02-11 15:47:42
Message-ID: 7972.1139672862@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-sql

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.

regards, tom lane

In response to

Responses

Browse pgsql-sql by date

  From Date Subject
Next Message Bryce Nesbitt 2006-02-11 19:48:07 Re: Very slow updates when using IN syntax subselect
Previous Message Bryce Nesbitt 2006-02-11 05:12:30 Re: Very slow updates when using IN syntax subselect