pg.ddx.io  pgsql-admin@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Dan Hrabarchuk <dan@kwasar.biz>
To: pgsql-admin@postgresql.org <pgsql-admin@postgresql.org>
Subject: Re: [Fwd: zero_damaged_pages having no effect]
Date: Tue, 12 Oct 2004 11:34:25 -0700
Message-ID: <1097606065.4495.15.camel@dan.geotivity.net> (raw)

Thank you Tom.

So in my case, where should I start? I want to be able to dump this
database to a new machine. Given my corruption, how should I go about
this? My current plan is to use Slony, but I'm worried that the
corruption will interfere with the transfer.

How can I get the db server to simply ignore errors? The data that is
lost can be recovered from the original source.

postgres[61834]: [184] PANIC:  open of /psql/pg_clog/0C95 failed: No
such file or directory

What would happen if I touched this file as the postgres user??

So there would be a 0 length file, with the proper ownership and
permissions.

Thanks once again.

Dan




Message-ID: <1097606065.4495.15.camel@dan.geotivity.net>
Permalink:  ../1097606065.4495.15.camel@dan.geotivity.net/
Also on:    postgresql.org/message-id/1097606065.4495.15.camel@dan.geotivity.net

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients from your mail client; the link fills in
  the headers below: reply via email
  Some clients, webmail especially, drop In-Reply-To and References from
  a link, and the reply then starts a new thread: use the mbox below.

  To: pgsql-admin@postgresql.org
  Cc: dan@kwasar.biz
  Subject: Re: [Fwd: zero_damaged_pages having no effect]
  In-Reply-To: <1097606065.4495.15.camel@dan.geotivity.net>
  References: <1097606065.4495.15.camel@dan.geotivity.net>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox