gnumed-bugs
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Gnumed-bugs] [Gnumed-devel] database version requirement switch: 9.


From: Busser, Jim
Subject: Re: [Gnumed-bugs] [Gnumed-devel] database version requirement switch: 9.1, was: Problem in git bootstrapping v18 to v19 db
Date: Wed, 17 Jul 2013 23:09:41 +0000

On 2013-07-17, at 2:39 PM, Karsten Hilbert <address@hidden> wrote:

> Note that it can often be a good idea to use the *newer*,
> improved (9.2) pg_dump to create dumps of an older PG for
> import into a newer one.

Absent any guidance how to do the above at

        http://www.postgresql.org/docs/current/static/app-pgdump.html

is it the case that, when one installs the new PG, one can simply then run the 
new pg_dump from inside the new

        .../bin/

except … how does it know where to access the (old) PG data?

The new installation might be configured to write and store data in

        /Library/PostgreSQL/9.2/data

whose clusters may, or may not, have been initialized with the updating, while 
the *data of interest* may exist inside

        /Library/PostgreSQL/8.4/data

so does any of what you propose depend on an 8.4 version of postmaster or 
server to be running, or to somehow "map" the old path as the data path?

-- Jim



        


reply via email to

[Prev in Thread] Current Thread [Next in Thread]