-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 > Something very bad has happened to pg_attribute. Just for a data point, this same problem happened to me on a 8.0 beta database. Actually, only one of 8 databases was affected for that particular backend, but that one was toast and I had to rebuild it from a backup. This was a pretty lightly used database, and certainly all the SQL used was pretty standard (no mucking with pg_attribute directly, as a google-searched thread of this problem insinuated). - -- Greg Sabino Mullane greg@xxxxxxxxxxxx PGP Key: 0x14964AC8 200503060137 http://biglumber.com/x/web?pk=2529DF6AB8F79407E94445B4BC9B906714964AC8 -----BEGIN PGP SIGNATURE----- iD8DBQFCKqVTvJuQZxSWSsgRArrEAJ4jZDILFDgtBF+8GAvMzeGvXsgcPACfbBZi 0zE2+vJbGxB5SePepObp6PY= =/XRk -----END PGP SIGNATURE----- ---------------------------(end of broadcast)--------------------------- TIP 4: Don't 'kill -9' the postmaster
