Re: 8.0 -> 8.1 dump duplicate key problem?
От | Merlin Moncure |
---|---|
Тема | Re: 8.0 -> 8.1 dump duplicate key problem? |
Дата | |
Msg-id | b42b73150511141144q20c57a0cjf5152b2a7370f886@mail.gmail.com обсуждение исходный текст |
Ответ на | Re: 8.0 -> 8.1 dump duplicate key problem? (Tom Lane <tgl@sss.pgh.pa.us>) |
Список | pgsql-hackers |
On 11/14/05, Tom Lane <tgl@sss.pgh.pa.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.38115077260 | 00136860 | 23 | 584415243 | 0 | 2005-09-15 09:32:18.89815082475 | 00136860 | 20 | 584527952 | 0 | 2005-09-15 11:17:17.06215082522 | 00136860 | 23 | 584527961 | 0 | 2005-09-15 11:17:17.187 (4 rows)
В списке pgsql-hackers по дате отправления: