I test it, but I can't reproduce on clean database cluster (after init).
Problem is that it was on our production database so I can't experiment
too much on it. So last night I backed up whole pgsql tree and I instaled
clean 7.2.1 instalation to our production environment. Now I will be able
to perform some deeper.
I remember only one event. There was HW crash on our server 2 month ago.
I transfered whole pgsql tree to a different computer. But there were no
problems until now. So I don't know if some file which could be corrupted
at that time could have influence to this data corruption.
Regards,
Vaclav
On Tue, 30 Apr 2002, Tom Lane wrote:
> Vaclav Kulakovsky <vaclav.kulakovsky@definity.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
>
> ---------------------------(end of broadcast)---------------------------
> TIP 6: Have you searched our list archives?
>
> http://archives.postgresql.org
>