Re: Bug #474: Index using problem

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Andreas Wernitznig <andreas(at)insilico(dot)com>
Cc: pgsql-bugs(at)postgresql(dot)org
Subject: Re: Bug #474: Index using problem
Date: 2001-10-05 19:15:06
Message-ID: 21296.1002309306@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

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

Browse pgsql-bugs by date

  From Date Subject
Next Message Andreas Wernitznig 2001-10-05 21:58:19 Re: Bug #474: Index using problem
Previous Message Andreas Wernitznig 2001-10-05 18:37:18 Re: Bug #474: Index using problem