From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | "scott(dot)marlowe" <scott(dot)marlowe(at)ihs(dot)com> |
Cc: | Dave Smith <dave(dot)smith(at)candata(dot)com>, "pgsql-general(at)postgresql(dot)org" <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: Vacuum Error |
Date: | 2004-01-12 22:57:52 |
Message-ID: | 5774.1073948272@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
"scott.marlowe" <scott(dot)marlowe(at)ihs(dot)com> writes:
>> Dave Smith <dave(dot)smith(at)candata(dot)com> writes:
>>> I am running 7.2 and when doing a vacuum I am getting the following
>>> error....
>>
>>> ERROR: Cannot insert a duplicate key into unique index
>>> pg_statistic_relid_att_index
> Didn't this happen with parallel vacuum / analyzes running in the olden
> days?
I don't think it could happen in 7.2, because that release took
ExclusiveLock on pg_statistic while inserting rows.
Later releases use a weaker lock (to permit concurrent ANALYZE of
different tables) and are subject to "concurrent update" errors if
you try to run two ANALYZEs of the same table at the same time.
But it doesn't sound like Dave is doing that, anyway.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Andrew Bartley | 2004-01-12 23:00:26 | Re: Vacuum Error |
Previous Message | Tom Lane | 2004-01-12 22:48:56 | Re: Column qualifier issue |