Re: Rows missing from table despite FK constraint

From: Alvaro Herrera <alvherre(at)commandprompt(dot)com>
To: Konrad Garus <konrad(dot)garus(at)gmail(dot)com>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Alban Hertroys <dalroi(at)solfertje(dot)student(dot)utwente(dot)nl>, pgsql-general(at)postgresql(dot)org
Subject: Re: Rows missing from table despite FK constraint
Date: 2010-01-08 16:53:40
Message-ID: 20100108165340.GC3635@alvh.no-ip.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

Konrad Garus escribió:
> 2010/1/8 Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>:
> > So, no wraparound problem ... odder and odder.  Could we see the whole
> > -i -f printout for that block?  You trimmed some of it before,
> > particularly the block header.
>
> Attached.
>
> Since data on disk looks correct, is it possible to diagnose it on a
> higher level? Could the damage be done by vacuum?

I'm a bit surprised by the block numbers in the block header vs. t_self ...
I would have guessed that they come from a different segment (and
the numbers seem to match, as 603713 % 131072 = 79425), but Konrad
doesn't seem to be using the foo.4 file.

--
Alvaro Herrera http://www.CommandPrompt.com/
The PostgreSQL Company - Command Prompt, Inc.

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Fernando Morgenstern 2010-01-08 16:55:26 Re: Table appears on listing but can't drop it
Previous Message Tom Lane 2010-01-08 16:48:33 Re: Table appears on listing but can't drop it