| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | "Michael Beckstette" <mbeckste(at)TechFak(dot)Uni-Bielefeld(dot)DE> |
| Cc: | pgsql-bugs(at)postgresql(dot)org |
| Subject: | Re: Missing tables in postgresql 7.2.4 |
| Date: | 2005-05-11 15:51:45 |
| Message-ID: | 4527.1115826705@sss.pgh.pa.us |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
"Michael Beckstette" <mbeckste(at)TechFak(dot)Uni-Bielefeld(dot)DE> writes:
> we recently discovered on our production database an a little bit bizarre
> problem (after two years stable operations). Some tables are simply missing, or
> sometimes the affected table(s) is/are there but not listed in pg_tables.
This sounds a bit like a transaction ID wraparound problem. Have you
been vacuuming your whole database on a reasonable schedule? The
missing tables might conceivably be old enough that their pg_class rows
have wrapped around "into the future". It'd be useful to look at
SELECT datname, age(datfrozenxid) FROM pg_database;
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bogdan Matei | 2005-05-11 15:56:28 | BUG #1660: Growing used memory and critical performance loss |
| Previous Message | Bruce Momjian | 2005-05-11 15:47:27 | Re: [BUGS] BUG #1588: pg_autovacuum sleep parameter overflow |