Re: 8.0 -> 8.1 dump duplicate key problem?

From: Merlin Moncure <mmoncure(at)gmail(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: pgsql-hackers(at)postgresql(dot)org
Subject: Re: 8.0 -> 8.1 dump duplicate key problem?
Date: 2005-11-14 19:44:23
Message-ID: b42b73150511141144q20c57a0cjf5152b2a7370f886@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 11/14/05, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:

> I think you need to try this with enable_indexscan = 0; it should be
> showing us 4 rows according to your prior result, and it's only showing

one thing I forgot to mention....there is a sequence on the table.
Sequence is global for all tables hooked via default on a
domain..highly unlikely records were inserted back to back.

esp=# select id, 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);
id | prl_combined_key | prl_seq_no | xmin | xmax | lastmod
----------+------------------+------------+-----------+------+-------------------------
15077227 | 00136860 | 20 | 584412245 | 0 |
2005-09-15 09:31:35.381
15077260 | 00136860 | 23 | 584415243 | 0 |
2005-09-15 09:32:18.898
15082475 | 00136860 | 20 | 584527952 | 0 |
2005-09-15 11:17:17.062
15082522 | 00136860 | 23 | 584527961 | 0 |
2005-09-15 11:17:17.187
(4 rows)

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Jaime Casanova 2005-11-14 19:45:53 Re: functions marked STABLE not allowed to do INSERT
Previous Message Merlin Moncure 2005-11-14 19:38:19 Re: 8.0 -> 8.1 dump duplicate key problem?