| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | "Matt Clark" <matt(at)ymogen(dot)net> |
| Cc: | "Murthy Kambhampaty" <murthy(dot)kambhampaty(at)goeci(dot)com>, "'Peter Eisentraut'" <peter_e(at)gmx(dot)net>, pgsql-admin(at)postgresql(dot)org |
| Subject: | Re: LVM snapshots |
| Date: | 2003-04-04 14:49:43 |
| Message-ID: | 5550.1049467783@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-admin |
"Matt Clark" <matt(at)ymogen(dot)net> writes:
> Does anyone know what (in general) would cause the notices that Murthy spotted in the logs as per the snippet below?
>> NOTICE: Rel <table name>: Uninitialized page 54300 - fixing
There is a known mechanism for this to occur on certain key system catalogs,
see http://fts.postgresql.org/db/mw/msg.html?mid=1357214
We've seen some reports suggesting it can happen on user tables too, but
I don't know what the mechanism is or whether there's any risk of data
loss. If you can make this happen reproducibly (or at least with decent
probability) on tables other than pg_class, pg_type, pg_attribute, pg_proc,
then I'd be real interested to see a test case.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Murthy Kambhampaty | 2003-04-04 15:09:01 | Re: LVM snapshots |
| Previous Message | bvidinli@yimpas.net.tr | 2003-04-04 13:57:13 | remove - unsubscribe |