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 <[EMAIL PROTECTED]> wrote:
> Andreas Wernitznig <[EMAIL PROTECTED]> 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
---------------------------(end of broadcast)---------------------------
TIP 2: you can get off all lists at once with the unregister command
(send "unregister YourEmailAddressHere" to [EMAIL PROTECTED])
