Re: serial type (text instead of integer) and duplicate keys - Mailing list pgsql-general

From Tom Lane
Subject Re: serial type (text instead of integer) and duplicate keys
Date
Msg-id 15491.1113315467@sss.pgh.pa.us
Whole thread Raw
In response to Re: serial type (text instead of integer) and duplicate keys  (Carlos Costa <ccosta@gmail.com>)
List pgsql-general
Carlos Costa <ccosta@gmail.com> writes:
> SELECT oid,xmin,xmax,ctid,id FROM articles WHERE id=391;
>    oid   |   xmin    |   xmax    |   ctid   | id
> ---------+-----------+-----------+----------+-----
>  3032469 | 152691945 | 152886684 |  (104,6) | 391
>  3032469 | 152886687 | 156995994 | (104,13) | 391
> (2 rows)

Could we see cmin,cmax as well?

Since the OID is the same, these are evidently two versions of the same
row; somehow one of them didn't get marked dead when the other one was
created.  What patterns of updating do you use on this table?  Any
SELECT FOR UPDATE?

            regards, tom lane

pgsql-general by date:

Previous
From: Tom Lane
Date:
Subject: Re: Question about Large Objects
Next
From: "Jeff Eckermann"
Date:
Subject: Re: Crystal reports 9 fails to recognise data on upgrade to 8.0.1