From: | "Paul Laughlin" <plaughlin(at)gmail(dot)com> |
---|---|
To: | "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | pgsql-bugs(at)postgresql(dot)org |
Subject: | Re: duplicate key violates unique constraint pg_toast_635216540 |
Date: | 2006-10-16 16:45:35 |
Message-ID: | f41e66d10610160945v75ee6f19kf7ee1c79a367265@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs |
warehouse=# select count(distinct chunk_id) from
pg_toast.pg_toast_635216540;
count
-------
74557
(1 row)
We're on version 8.0.7
On 10/16/06, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
>
> "Paul Laughlin" <plaughlin(at)gmail(dot)com> writes:
> > For the last 6 months or so we've had an intermittent issue while doing
> a
> > data import with a simple update statement. The fix that we've found
> for
> > this issue is to REINDEX TABLE <tablename>;
>
> What PG version is this?
>
> Are you sure that the REINDEX actually does anything, as opposed to
> merely retrying the data import? I'm thinking you may be having
> problems with OID collisions after OID wraparound, which is something
> 8.1 should defend against but no earlier version does.
>
> What do you get from
> select count(distinct chunk_id) from pg_toast.pg_toast_635216540 ;
>
> regards, tom lane
>
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2006-10-16 16:51:08 | Re: duplicate key violates unique constraint pg_toast_635216540 |
Previous Message | Tom Lane | 2006-10-16 16:25:12 | Re: duplicate key violates unique constraint pg_toast_635216540 |