Skip site navigation (1) Skip section navigation (2)

Re: Bug #474: Index using problem

From: Andreas Wernitznig <andreas(at)insilico(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: pgsql-bugs(at)postgresql(dot)org
Subject: Re: Bug #474: Index using problem
Date: 2001-10-05 21:58:19
Message-ID: 20011005235819.2e0e1639.andreas@insilico.com (view raw or flat)
Thread:
Lists: pgsql-bugs
Why don't you skip the automatic index creation for primary keys and let the user decide to create an index,
that should be used in any case, regardless what the query planner recommends ?

On Fri, 05 Oct 2001 15:15:06 -0400
Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:

> Andreas Wernitznig <andreas(at)insilico(dot)com> writes:
> > -> Using one connection the optimizer for pk/fk-checking is not
> > updated by a "vacuum analyze".
> 
> Oh, I misunderstood you the first time: I thought you were saying that
> *other* backends couldn't see the results of the VACUUM.
> 
> The reason for this behavior is that the foreign key checker caches a
> plan for each foreign-key-checking query the first time it needs to
> use that query (within a given backend).  There should be a mechanism
> to flush those cached plans when circumstances change ... but currently
> there isn't.
> 
> 			regards, tom lane

In response to

Responses

pgsql-bugs by date

Next:From: Tom LaneDate: 2001-10-05 22:01:08
Subject: Re: Bug #474: Index using problem
Previous:From: Tom LaneDate: 2001-10-05 19:15:06
Subject: Re: Bug #474: Index using problem

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group