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

[Busser, Jim]

On 2013-11-19, at 3:12 PM, Jim Busser <address@hidden> wrote:

> seemingly needing a PGPORT environmental variable to repoint to 5433:
> 
>       echo $PGPORT
> 
>       (nothing)
> 
>       export PGPORT=5433
>       pg_dump -Fc -f gnumedv18.backup gnumed_v18
>       pg_dumpall --globals-only > globals.sql

oops

I believe the above dump and dumpall were meant to operate using the binaries 
located in

        /Library/PostgreSQL/9.3/bin/

but needing to connect to the *old* postgres under which the 8.4 database was 
living (prior to being pulled up into the new PostgreSQL structure).

Accordingly, the above

        pg_dump -Fc -f gnumedv18.backup gnumed_v18
        pg_dumpall --globals-only > globals.sql

need to be operating on port 5432 in order to connect to the old postgres and if

        export PGPORT=5433

is issued prematurely, this environment variable will cause the dump and 
dumpall to fail. They only worked for me (on 5433) because I had already pulled 
gnumed_v18 up into PostgreSQL 9.3 in an earlier session.

However, we *do* want the pg_restore to be utilizing the new postgres server 
(9.3) for

        pg_restore --dbname postgres --create gnumedv18.backup

-- JIm