| From: | Alvaro Herrera <alvherre(at)commandprompt(dot)com> |
|---|---|
| To: | Philip Warner <pjw(at)rhyme(dot)com(dot)au> |
| Cc: | pgsql-bugs(at)postgresql(dot)org, Michael Fuhr <mike(at)fuhr(dot)org> |
| Subject: | Re: BUG #2379: Duplicate pkeys in table |
| Date: | 2006-04-06 14:27:23 |
| Message-ID: | 20060406142723.GD15753@surnet.cl |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
Philip Warner wrote:
> # set enable_indexscan=off;
> # SELECT xmin, xmax, cmin, cmax FROM xxx where id = 24613;
> xmin | xmax | cmin | cmax
> ----------+----------+------+----------
> 32902771 | 0 | 20 | 32902872
> 32902771 | 0 | 20 | 32902872
> 32902771 | 0 | 20 | 32902872
> 32902771 | 0 | 20 | 32902872
> 32902771 | 0 | 20 | 32902872
> 32902771 | 33048159 | 20 | 20
> (6 rows)
Ugh.
Do the triggers involved have EXCEPTION clauses? (I assume they are
written in PL/pgSQL -- are there any in other languages?)
--
Alvaro Herrera http://www.CommandPrompt.com/
The PostgreSQL Company - Command Prompt, Inc.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Philip Warner | 2006-04-06 14:39:08 | Re: BUG #2379: Duplicate pkeys in table |
| Previous Message | Tom Lane | 2006-04-06 14:24:15 | Re: BUG #2379: Duplicate pkeys in table |