| From: | Craig Ringer <ringerc(at)ringerc(dot)id(dot)au> |
|---|---|
| To: | Jeff Davis <pgsql(at)j-davis(dot)com> |
| Cc: | "pgsql-general(at)postgresql(dot)org" <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: Odd corruption issue reported on dba.stackexchange.com, need advice |
| Date: | 2012-07-24 01:16:17 |
| Message-ID: | 500DF761.4090309@ringerc.id.au |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On 07/24/2012 08:48 AM, Jeff Davis wrote:
> On Thu, 2012-07-19 at 11:35 +0800, Craig Ringer wrote:
>> The short version is that the person did a bulk-load of some PostGIS
>> data using the osm2pgsql data-loader tool
>> ( http://wiki.openstreetmap.org/wiki/Osm2pgsql) to populate a Pg 9.1
>> database. This appeared to succeed, but when the server was restarted
>> it failed to come up, complaining that "WAL contains references to
>> invalid pages" and "page 1493172 of relation base/16385/477861 was
>> uninitialized" (for many different pages).
>>
>> The logs of the shutdown suggest that a backend probably crashed, but
>> that shouldn't cause the WAL and heap corruption observed by the OP.
> Is it possible that the machine has write cache enabled?
It shouldn't matter - only PostgreSQL was restarted, not the whole
machine - and cleanly at that. Very strange.
--
Craig Ringer
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Adam Crews | 2012-07-24 02:02:45 | Re: postgres 9 bind address for replication |
| Previous Message | Jeff Davis | 2012-07-24 00:48:51 | Re: Odd corruption issue reported on dba.stackexchange.com, need advice |