pg.ddx.io  pgsql-admin@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Andrew Farmer <mail@andrewfarmer.com>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: pgsql-admin@postgresql.org
Subject: Re: 7.3.4 Table corruption
Date: Fri, 27 Aug 2004 13:03:59 +0900
Message-ID: <412EB2AF.1080502@andrewfarmer.com> (raw)
In-Reply-To: <10928.1093485410@sss.pgh.pa.us>
References: <412BEE3D.8070409@andrewfarmer.com>
	<10928.1093485410@sss.pgh.pa.us>

Thanks for the advice.  I'll relax the constraints on the table, and 
reload that table from the dump, might take a while to fix any problems, 
but it should be safer.

Regards, Andrew

Tom Lane wrote:

>Andrew Farmer <mail@andrewfarmer.com> writes:
>  
>
>>My question is, if I load the good dump into a clean database, and then 
>>find the underlying file that represents the broken table and copy it 
>>over the top of the broken table, am I likely to face any big problems?
>>    
>>
>
>This strikes me as a real good way to shoot yourself in the foot ;-).
>Better take a backup and be prepared to restore from it.  And I'd
>suggest experimenting in a scratch installation before you try it for
>real.
>
>Having said that, I think it would work, if your "clean database" is
>another DB in the same cluster (you could *not* copy from data prepared
>under a different postmaster).  And you'll need to copy all the indexes
>on that table, and its toast table and toast table index if it has one.
>And shut down the postmaster while you do the copying.
>
>			regards, tom lane
>
>---------------------------(end of broadcast)---------------------------
>TIP 4: Don't 'kill -9' the postmaster
>
>  
>




view thread (3+ messages)

Message-ID: <412EB2AF.1080502@andrewfarmer.com>
Permalink:  ../412EB2AF.1080502@andrewfarmer.com/
Also on:    postgresql.org/message-id/412EB2AF.1080502@andrewfarmer.com

 · 

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: mail@andrewfarmer.com, tgl@sss.pgh.pa.us
  Subject: Re: 7.3.4 Table corruption
  In-Reply-To: <412EB2AF.1080502@andrewfarmer.com>
  References: <412BEE3D.8070409@andrewfarmer.com> <10928.1093485410@sss.pgh.pa.us> <412EB2AF.1080502@andrewfarmer.com>

* 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