| From: | "scott(dot)marlowe" <scott(dot)marlowe(at)ihs(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| 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:27:26 |
| Message-ID: | Pine.LNX.4.33.0401121527080.20494-100000@css120.ihs.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Mon, 12 Jan 2004, Tom Lane wrote:
> 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
>
> Hmm, if it were a slightly newer version I'd be interested in how you
> got into this state, but since it's 7.2 I'll write it off as an old
> bug. The easiest way out, seeing that pg_statistic is all derived data,
> is just
> DELETE FROM pg_statistic;
> (possibly VACUUM FULL pg_statistic here)
> re-ANALYZE everything
> You should try the nearby suggestion to REINDEX first, but I'm betting
> that that doesn't help.
Didn't this happen with parallel vacuum / analyzes running in the olden
days?
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Alex Satrapa | 2004-01-12 22:31:06 | Re: Dump tables with pg_dump - no or different Owner |
| Previous Message | Tom Lane | 2004-01-12 22:27:13 | Re: Case sensitivity |