gnumed-devel
[Top][All Lists]
Advanced

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

Re: [Gnumed-devel] Solved: Upgrade Postgresql for GNUmed on Windows


From: Karsten Hilbert
Subject: Re: [Gnumed-devel] Solved: Upgrade Postgresql for GNUmed on Windows
Date: Tue, 19 Nov 2013 19:02:07 +0100
User-agent: Mutt/1.5.21 (2010-09-15)

On Tue, Nov 19, 2013 at 05:56:55PM +0000, Jim Busser wrote:

> My impression had been that in the process of upgrading, one is supposed to 
> use the new binaries in place of the old ones.
> 
> This seems the case not just for pg_upgrade, but also for pg_dump and 
> pg_dumpall (as already commented upon):
> 
>       On 2013-11-19, at 3:49 AM, Karsten Hilbert <address@hidden> wrote:
> 
> >     On Sun, Nov 17, 2013 at 02:19:29PM +0100, Hilbert, Sebastian wrote:
> > 
> >>    One major showstopper seems to be if one uses pg_dumpall from the older 
> >>    postgres (PG 8.4). When using pg_dumpall from PG 9.2 the errors seem to 
> >> go 
> >>    away.
> > 
> >     This is absolutely the procedure recommended by the PostgreSQL team.
> 
> despite that I would have thought "restore" should be able
> to restore something created by earlier tools. However maybe
> that is only (somewhat) reliable for individual databases and
> not the entirety of the earlier postgresql installation.

The approach taken by PostgreSQL is that newer tools
know how to pull backups from old servers in improved
ways. This is much safer than attempting to mangle
old and potentially arbitrary data files.

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



reply via email to

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