From: | Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | Vaclav Kulakovsky <vaclav(dot)kulakovsky(at)definity(dot)cz>, pgsql-general(at)postgresql(dot)org |
Subject: | Re: Data integrity problem !!! |
Date: | 2002-05-25 23:56:58 |
Message-ID: | 200205252356.g4PNuwM27505@candle.pha.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Tom Lane wrote:
> Vaclav Kulakovsky <vaclav(dot)kulakovsky(at)definity(dot)cz> writes:
> > I've started investigate a cause and I've found that there are really
> > duplicated PK in table and some data in the same rows are corrupted. I
> > I've checked all log files and database backups and found that this
> > problem arose probably after run VACUUM ANALYZE command which is executed
> > every night. Everning DB backup was ok and morning backup contained these
> > errors. There were no user activity between these 2 backups except VACUUM
> > ANALYZE command.
>
> Hmm. Can you reproduce the problem from a standing start? (Ie, initdb,
> load your evening backup, vacuum analyze, look for duplicates.) This
> is a worrisome report but I really see nothing we can do without more
> information. A test case would be great.
The user reported they were running 7.2. I assume they got bitten by
the sequence counter bug we fixed in 7.2.1. They just upgraded to 7.2.1
so I assume the problem will not happen again.
--
Bruce Momjian | http://candle.pha.pa.us
pgman(at)candle(dot)pha(dot)pa(dot)us | (610) 853-3000
+ If your life is a hard drive, | 830 Blythe Avenue
+ Christ can be your backup. | Drexel Hill, Pennsylvania 19026
From | Date | Subject | |
---|---|---|---|
Next Message | Alan Wayne | 2002-05-26 03:41:02 | simple e-mail question. |
Previous Message | Stephan Szabo | 2002-05-25 22:52:27 | Re: Removing Referential Integrity |