Re: FAQ -- 'cache lookup failed' still a puzzle - Mailing list pgsql-general

From Stephan Szabo
Subject Re: FAQ -- 'cache lookup failed' still a puzzle
Date
Msg-id 20020313103106.I84314-100000@megazone23.bigpanda.com
Whole thread Raw
In response to FAQ -- 'cache lookup failed' still a puzzle  (will trillich <will@serensoft.com>)
Responses Re: FAQ -- 'cache lookup failed' still a puzzle
List pgsql-general
> the rule that intercepts 'insert' works like a charm -- and the
> primary difference is that the 'update' rule (above) calls
> stage_change() where the create rule doesn't need to -- so i
> thought that might be the culprit:
>
>     db> select stage_change(0,1,1);
>      stage_change
>     --------------
>                 0
>     (1 row)
>
> so it's not. or at least it's got *me* convinced, anyhow.

Well, it's not going to be referenced by name any more, it'll be
referenced by oid which is changed when you drop and create
it again.  You'd need to drop and create the rule again as well.


pgsql-general by date:

Previous
From: DaVinci
Date:
Subject: Referential integrity violation
Next
From: "Patrick L. Nolan"
Date:
Subject: Looking for information about rtree index