From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Vaclav Kulakovsky <vaclav(dot)kulakovsky(at)definity(dot)cz> |
Cc: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: Data integrity problem !!! |
Date: | 2002-04-30 14:53:07 |
Message-ID: | 20188.1020178387@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
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.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Martín Marqués | 2002-04-30 14:54:26 | Re: pgdump 7.2 on pg-7.1 |
Previous Message | Jean-Michel POURE | 2002-04-30 14:46:33 | Re: pgdump 7.2 on pg-7.1 |