On Mon, 2005-11-14 at 14:51 -0500, Tom Lane wrote: > Merlin Moncure <[EMAIL PROTECTED]> writes: > > esp=# select prl_combined_key, prl_seq_no, xmin, xmax, lastmod from > > parts_order_line_file where prl_combined_key = ' 00136860' and > > prl_seq_no in (20, 23); > > prl_combined_key | prl_seq_no | xmin | xmax | lastmod > > ------------------+------------+-----------+------+------------------------- > > 00136860 | 20 | 584527952 | 0 | 2005-09-15 11:17:17.062 > > 00136860 | 20 | 584412245 | 0 | 2005-09-15 09:31:35.381 > > 00136860 | 23 | 584527961 | 0 | 2005-09-15 11:17:17.187 > > 00136860 | 23 | 584415243 | 0 | 2005-09-15 09:32:18.898 > > OK, so the fact that they all have xmax=0 proves that none are UPDATEd > versions of others, which leaves us with the presumption that there was > an outright failure of duplicate-key detection during INSERT :-(
Is there any chance it is related to the 8.0 problem I reported on Wednesday? http://groups.google.ca/group/pgsql.hackers/browse_frm/thread/a832e9919fb53f92/83e8f0bd272b8597?lnk=st&q=%22possible+savepoint+bug%22&rnum=1&hl=en#83e8f0bd272b8597 -- ---------------------------(end of broadcast)--------------------------- TIP 4: Have you searched our list archives? http://archives.postgresql.org
