From: Peter Eisentraut <peter_e@gmx.net>
To: pgsql-sql@postgresql.org
Cc: Bryce Nesbitt <bryce1@obviously.com>
Subject: Re: Very slow updates when using IN syntax subselect
Date: Sat, 11 Feb 2006 21:34:57 +0100
Message-ID: <200602112134.57572.peter_e@gmx.net> (raw)
In-Reply-To: <43EE3F77.6020108@obviously.com>
References: <43ECFF0B.80905@obviously.com>
<7972.1139672862@sss.pgh.pa.us>
<43EE3F77.6020108@obviously.com>
Bryce Nesbitt wrote:
> > 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?
I'm sure you wouldn't appreciate it if PostgreSQL did a full table scan
before each query to figure out the total size of the involved tables.
--
Peter Eisentraut
http://developer.postgresql.org/~petere/
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: peter_e@gmx.net, bryce1@obviously.com
Subject: Re: Very slow updates when using IN syntax subselect
In-Reply-To: <200602112134.57572.peter_e@gmx.net>
* 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