Re: [Gnumed-bugs] [Gnumed-devel] database version requirement switch: 9.1, was: Problem in git bootstrapping v18 to v19 db

[Karsten Hilbert]

On Wed, Jul 17, 2013 at 11:09:41PM +0000, Jim Busser wrote:
> Date: Wed, 17 Jul 2013 23:09:41 +0000
> From: "Busser, Jim" <address@hidden>
> To: "address@hidden" <address@hidden>
> Subject: Re: [Gnumed-bugs] [Gnumed-devel] database version requirement
>  switch: 9.1, was: Problem in git bootstrapping v18 to v19 db
> 
> 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?

You tell it port and host where the old PG server runs.

Karsten


> 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
> 
> 
> 
>       

-- 
GPG key ID E4071346 @ gpg-keyserver.de
E167 67FD A291 2BEA 73BD  4537 78B9 A9F9 E407 1346