Re: Problem restoring Database

From: Richard Huxton <dev(at)archonet(dot)com>
To: mike <mike(at)redtux1(dot)uklinux(dot)net>, pgsql-general(at)postgresql(dot)org
Subject: Re: Problem restoring Database
Date: 2004-04-01 12:05:28
Message-ID: 200404011305.28665.dev@archonet.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On Thursday 01 April 2004 16:56, mike wrote:
> I have just upgraded froom Fedora test1 to test2 which has upgraded
> postgres version from 7.4.2 to 7.4.5 (frrom rpm -q)

Clever, since 7.4.5 hasn't been released yet. If that's actually what it says,
consider getting in touch with the packager, it should probably be 7.4.2-5.
Oh, between minor versions (e.g. 7.4.1 => 7.4.99) you don't need to
dump/restore, you can leave the files in-place. It's only when you go from
7.4 to 7.5 you need to dump/restore.

> I have used pg_dumpall to dump my database, the restore appeared to go
> OK, except there is no data in two of my tables (only these two)

You don't have to restore into a database, you can just redirect stdout to a
file:

pg_restore --table=tb_invoice_header mydumpfile > dump-invoice-headers.txt

You can manually import this using psql then. I'm a little puzzled as to how
this can happen without any error messages though - might you have missed
one?

--
Richard Huxton
Archonet Ltd

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Shridhar Daithankar 2004-04-01 12:15:01 Re: [Fwd: Help with Conversion]
Previous Message Richard Huxton 2004-04-01 12:01:21 Re: 7.2.3-7.4.2 migration