Skip site navigation (1) Skip section navigation (2)

Re: 7.2b3 pg_dump, general 7.2b3 comments

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Joe Conway <joseph(dot)conway(at)home(dot)com>
Cc: "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: 7.2b3 pg_dump, general 7.2b3 comments
Date: 2001-11-29 05:46:17
Message-ID: 15265.1007012777@sss.pgh.pa.us (view raw or flat)
Thread:
Lists: pgsql-hackers
Joe Conway <joseph(dot)conway(at)home(dot)com> writes:
> Is pg_dump supposed to work against prior version databases? I was
> moving data from an old server (running 7.2devel from several months
                      ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
> ago) to a new server (running 7.2b3), using pg_dump on the *new* server,
> and got the following message:

> # pg_dump -h 172.16.1.84 -U postgres -t el_names -i lt_lcat > el_names.dmp
> Password: <types in password>
> pg_dump: query to obtain list of tables failed: ERROR:  Attribute
> 'relhasoids' not found

Oh, never mind: I see it.  pg_dump's test is on whether the server calls
itself 7.2 or not.  You've evidently got a copy from back before the
changes to make OIDs optional.  The versioning code is not set up to
deal with intermediate development versions, so it gets it wrong about
what query to use.  You'll need to use the pg_dump of the same vintage
as the 7.2devel server.

You're a brave man to be putting production data on CVS-tip servers.
I wouldn't recommend it ;-)

			regards, tom lane

In response to

Responses

pgsql-hackers by date

Next:From: Tom LaneDate: 2001-11-29 05:50:50
Subject: Re: 7.2beta3 on Digital Alpha
Previous:From: Tom LaneDate: 2001-11-29 05:40:25
Subject: Re: Sequence docs

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group