Re: referential integrity violation - key referenced from - Mailing list pgsql-bugs

From Luiz Henrique
Subject Re: referential integrity violation - key referenced from
Date
Msg-id ba0a1f30608040730n308196bbw7972aa8f70d3458b@mail.gmail.com
Whole thread Raw
In response to Re: referential integrity violation - key referenced from  (Stephan Szabo <sszabo@megazone.bigpanda.com>)
Responses Re: referential integrity violation - key referenced from  (Stephan Szabo <sszabo@megazone.bigpanda.com>)
List pgsql-bugs
Hi, could you tell me how postgresql look for a referenced key? It looks in
table index? Maybe only the index is corrupted?

Thanks!

On 8/2/06, Stephan Szabo <sszabo@megazone.bigpanda.com> wrote:
>
> On Wed, 2 Aug 2006, Luiz Henrique wrote:
>
> > Hi,
> >
> > I'm running Postgresql 7.3 in Debian Woody OS.
> >
> > After some time working properly, insert's statements related this
> error:
> >
> > ----
> > referential integrity violation - key referenced from xxx not found in
> yyy
> > ----
> >
> > This error would be normal, if the key really doesn't exist, but the key
> > exist.
> > The insert's work some times, and some times don't.
> >
> >
> > Is there any file corrupted?
>
> It's hard to say. I'd have expected that a select * from parent where
> key=value would fail for both the fk check and for a check to see if the
> key exists assuming they used the same plan.  Can you make a standalone
> test case?
>
> > Removing the fk constraint would resolve the problem?
>
> Well, it'd stop the message, but if there is corruption, it wouldn't fix
> that.
>
> ---------------------------(end of broadcast)---------------------------
> TIP 5: don't forget to increase your free space map settings
>

pgsql-bugs by date:

Previous
From: "IvankoB"
Date:
Subject: BUG #2562: In rules: recalculation of input expression on each access
Next
From: Tom Lane
Date:
Subject: Re: Restoring 7.4 "pg_dumpall -o" output in 8.1 fails