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.
Tom Lane wrote:
>Andrew Farmer <mail(at)andrewfarmer(dot)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
>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
In response to
pgsql-admin by date
|Next:||From: Cris Carampa||Date: 2004-08-27 06:43:56|
|Subject: Compatibility between different versions of psql client and postgresql
|Previous:||From: Tom Lane||Date: 2004-08-27 03:29:21|
|Subject: Re: regression database |