Re: Searching for a supposedly resolved bug report

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Scott Eade <seade@xxxxxxxxxxxxxxxxxxxx> writes:
> Environment: PostgreSQL 7.3.10-RH, RHEL3
>     PANIC: open of /var/lib/pgsql/data/pg_clog/0058 failed: No such file
> or directory

> I am wondering if anyone can point me to the supposedly fixed bug that
> would have caused this (is it just me or is it difficult to find
> specific bugs using the mailing list - is there an issue tracker
> somewhere?)  It would be nice to know how to avoid this in the future.

I suppose Neil is thinking of this:

http://archives.postgresql.org/pgsql-hackers/2004-10/msg00464.php

which is in fact fixed as of 7.3.8 --- but if you'd updated a pre-7.3.8
installation to 7.3.10 then damage from a previous triggering of the bug
could possibly still be lurking.

Or you could have been bit by something else that happens to have a
similar-looking symptom.  There's not enough info here to say.

			regards, tom lane

---------------------------(end of broadcast)---------------------------
TIP 1: if posting/reading through Usenet, please send an appropriate
       subscribe-nomail command to majordomo@xxxxxxxxxxxxxx so that your
       message can get through to the mailing list cleanly

[Index of Archives]     [KVM ARM]     [KVM ia64]     [KVM ppc]     [Virtualization Tools]     [Spice Development]     [Libvirt]     [Libvirt Users]     [Linux USB Devel]     [Linux Audio Users]     [Yosemite Questions]     [Linux Kernel]     [Linux SCSI]     [XFree86]

  Powered by Linux