From: | Rod Taylor <pg(at)rbt(dot)ca> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | Merlin Moncure <mmoncure(at)gmail(dot)com>, pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: 8.0 -> 8.1 dump duplicate key problem? |
Date: | 2005-11-14 20:12:10 |
Message-ID: | 1131999130.7495.60.camel@home |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Mon, 2005-11-14 at 14:51 -0500, Tom Lane wrote:
> Merlin Moncure <mmoncure(at)gmail(dot)com> 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?
--
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2005-11-14 20:23:41 | Re: 8.0 -> 8.1 dump duplicate key problem? |
Previous Message | Jim C. Nasby | 2005-11-14 20:09:41 | Re: functions marked STABLE not allowed to do INSERT |