[Top][All Lists]

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

Re: [Gnumed-devel] Restoring a database under Debian

From: Busser, Jim
Subject: Re: [Gnumed-devel] Restoring a database under Debian
Date: Wed, 14 Jan 2015 22:04:49 +0000

On 2015-01-14, at 1:37 PM, Karsten Hilbert <address@hidden> wrote:

> On Wed, Jan 14, 2015 at 07:38:02PM +0000, Jim Busser wrote:
>>> I'll adjust the script to be more resilient. In the meantime
>>> please re-run with the _full_ path to the backup file given
>>> to the script.
>> Closer … inside the Debian (VirtualBox) VM, within my normal user account 
>> (jim), I downloaded server 20.0 tarball and then as root, changed into the 
>> server directory
>>      cd downloads/gnumed-server.20.0/server
>> but before proceeding, because I now have postgres 9.1 and 9.4 running in 
>> this vm which might cause port confusion, I checked their status …
>>      /usr/bin/pg_lsclusters
>> giving me
>>      Ver Cluster Port Status Owner Data directory Log file
>>      9.1 main 5432 online postgres /var/lib/postgresql/9.1/main 
>> /var/log/postgresql/postgresql-9.1-main.log
>>      9.4 main 5433 online postgres /var/lib/postgresql/9.4/main 
>> /var/log/postgresql/postgresql-9.4-main.log 
>> and so to ensure that when the restore script calls the right port, I took 
>> the precaution of
>>      PGPORT=5433; export PGPORT
> BTW, is there any specific reason why you are restoring into
> PostgreSQL 9.4 ?  IMHO it just complicates things (witness
> the need for defining the port).

Because I misbelieved 9.2 (or higher) to be required for client 1.5 however I 
now realize (on re-consulting this posting of yours from September):
that the requirement for ≥ 9.2 won't come until 1.6 (v21).

I was thinking that for my debian VM wheezy's postgres 9.1 -- unless doing so 
would cause problems -- I would just uninstall it, and then set 9.4 back to use 
port 5432.

-- Jim

reply via email to

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