On Thu, Feb 7, 2013 at 1:44 AM, Pavan Deolasee <pavan.deola...@gmail.com> wrote: > On Thu, Feb 7, 2013 at 2:25 PM, Pavan Deolasee <pavan.deola...@gmail.com> > wrote: > >> >> Will look more into it, but thought this might be useful for others to >> spot the problem. >> > > And here is some more forensic info about one of the pages having > duplicate tuples. > > jjanes=# select *, xmin, xmax, ctid from foo where index IN (select > index from foo group by index having count(*) > 1 ORDER by index) > ORDER by index LIMIT 3; > index | count | xmin | xmax | ctid > -------+-------+------------+------+----------- > 219 | 353 | 2100345903 | 0 | (150,98) > 219 | 354 | 2100346051 | 0 | (150,101) > 219 | 464 | 2101601086 | 0 | (150,126) > (3 rows)
The one where count=464 should be the correct one to be visible, and the other two are old tuples that were updated away. (The test driver increases the count column monotonically for each any given value of index column. Cheers, Jeff -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
