| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> |
| Cc: | "Rajesh Kumar Mallah(dot)" <mallah(at)trade-india(dot)com>, pgsql-admin(at)postgresql(dot)org |
| Subject: | Re: VACUUM warning message. |
| Date: | 2003-01-27 21:52:19 |
| Message-ID: | 8369.1043704339@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-admin |
Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> writes:
> I assume this is 7.2.X. I know this is fixed in 7.3.1 but I am not sure
> what release we fixed it in. The HISTORY file doesn't have a specific
> mention of the fix. It is not something to be worried about, as I
> remember.
Mmm, I'm not sure. The known variant of this problem only affects certain
system tables (the nailed-in-cache ones):
http://archives.postgresql.org/pgsql-hackers/2002-11/msg00486.php
This is evidently a user table:
> WARNING: Rel site_search: Uninitialized page 1 - fixing
I'd wonder about hardware failures, myself. Does the table appear
to have lost a lot of rows that should have been there?
Other interesting questions are whether the table has recently undergone
a TRUNCATE, or deletion of a large fraction of its rows followed by
VACUUM (probably VACUUM FULL).
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andrew Sullivan | 2003-01-27 23:18:20 | Re: Replication |
| Previous Message | Tom Lane | 2003-01-27 21:02:54 | Re: Cannot connect to the database (PG 7.3) |