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

[Busser, Jim]

On 2013-11-19, at 2:25 AM, Karsten Hilbert <address@hidden> wrote:

> On Tue, Nov 19, 2013 at 08:12:04AM +0000, Jim Busser wrote:
> 
>>>>> 8.) type: pg_dump -p 5432 -Fc -f gnumedv18.backup gnumed_v18
>>>>> 
>>>>> 9.) type: pg_dumpall --globals-only > globals.sql
>>>> 
>>>> I think the above needs to be
>>>> 
>>>>    pg_dumpall -p 5432 --globals-only > globals.sql
>>> 
>>> That's safer but not required as 5432 is the default
>>> port unless reconfigured.
>> 
>> As would have been achieved from steps 2-5 taken earlier in the sequence:
>> 
>> - in Step 2, self-installation of the new postgres on port 5433 and
>> 
>> - in Step 6, SET PATH=%PATH%;C:\Programme\PostgreSQL\9.3\bin
> 
> Neither step reconfigures the default port 5432 of
> PG 8.4 as far as I can see.

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.

-- Jim