Re: Rows missing from table despite FK constraint

2010/1/8 Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>:

> Also, what are the XMINs of the non-missing tuples in the adjacent
> blocks?

# /usr/lib/postgresql/8.3/bin/pg_controldata /var/lib/postgresql/8.3/main/
pg_control version number: 833
Catalog version number: 200711281
Database system identifier: 5246886698902745063
Database cluster state: in production
pg_control last modified: Fri 08 Jan 2010 10:20:56 AM CST
Latest checkpoint location: 1D6/186B6BA0
Prior checkpoint location: 1D6/165DAF60
Latest checkpoint's REDO location: 1D6/174C8FB8
Latest checkpoint's TimeLineID: 1
Latest checkpoint's NextXID: 0/83037806
Latest checkpoint's NextOID: 142180690
Latest checkpoint's NextMultiXactId: 2250472
Latest checkpoint's NextMultiOffset: 5954794
Time of latest checkpoint: Fri 08 Jan 2010 10:18:33 AM CST
Minimum recovery ending location: 0/0
Maximum data alignment: 8
Database block size: 8192
Blocks per segment of large relation: 131072
WAL block size: 8192
Bytes per WAL segment: 16777216
Maximum length of identifiers: 64
Maximum columns in an index: 32
Maximum size of a TOAST chunk: 1996
Date/time type storage: 64-bit integers
Maximum length of locale name: 128
LC_COLLATE: en_US.UTF-8
LC_CTYPE: en_US.UTF-8

2 mins around the missing rows:

ctid | xmin | attachment_id
-------------+----------+---------------
(603712,67) | 17140362 | 15460680
(603712,69) | 17140363 | 15460871
(603712,71) | 17140364 | 15460681
(603712,73) | 17140368 | 15460872
(603712,75) | 17140369 | 15460682
(603712,78) | 17140373 | 15460873
(603714,1) | 17140379 | 15460685
(603714,3) | 17140380 | 15460473
(603714,5) | 17140381 | 15460875
(603714,7) | 17140382 | 15460686
(603714,9) | 17140383 | 15460474

--
Konrad Garus