BUG #2489: Metadata dosen't match tables
The following bug has been logged online:
Bug reference: 2489
Logged by: James A Cole
Email address: jacole@acm.org
PostgreSQL version: 7.4.13
Operating system: Red Hat Enterprise Linux 4
Description: Metadata dosen't match tables
Details:
PostgreSQL 7.4.13 on i386-redhat-linux-gnu, compiled by GCC
i386-redhat-linux-gcc (GCC) 3.4.6 20060404 (Red Hat 3.4.6-2)
mkeB_reports=# \d arrivals
Did not find any relation named "arrivals".
mkeB_reports=# select * from arrivals where ontime>'2006-6-21';
ontime | flightid | airline | runway | upline | downline |
acty
pe | sta | beacon | icao24 | tail | term |
gate
| etatype | cetatime
------------------------+----------+---------+--------+--------+----------+-
----
---+------------------------+--------+----------+----------+----------+-----
----
-+---------+-------------------------------
2006-06-21 00:16:52-04 | ACT301 | ACT | 01L | MDW | MKE |
PA31
| | | | | |
| 8 | 2006-06-21 00:18:29.538826-04
2006-06-21 01:04:08-04 | USC361 | USC | 01L | MDW | MKE |
C208
| | | | | |
| 8 | 2006-06-21 01:05:53.170079-04
There are many other databases on this server. Most
do not have this problem.
Jim Cole
James A Cole wrote:
mkeB_reports=# \d arrivals
Did not find any relation named "arrivals".mkeB_reports=# select * from arrivals where ontime>'2006-6-21';
[data]
There are many other databases on this server. Most
do not have this problem.
Ah, so this is the only one that has suffered transaction id wraparound.
If you don't want to restore from backup, you may want to search the
archives for old threads. Use keywords "transaction id wraparound" or
maybe "xid wraparound".
Next time you really want to make sure you vacuum the whole database,
often.
--
Alvaro Herrera http://www.CommandPrompt.com/
PostgreSQL Replication, Consulting, Custom Development, 24x7 support
"James A Cole" <jacole@acm.org> writes:
mkeB_reports=# \d arrivals
Did not find any relation named "arrivals".
mkeB_reports=# select * from arrivals where ontime>'2006-6-21';
[ works ]
Looks like XID wraparound in the system catalogs. You can probably get
out of it with a database-wide VACUUM, but there is some risk that
you've lost data. Please read the administrator's guide part of the
manual concerning routine vacuuming requirements.
regards, tom lane