gnumed-bugs
[Top][All Lists]
Advanced

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

Re: [Gnumed-bugs] [Gnumed-devel] database version requirement switch: 9.


From: Karsten Hilbert
Subject: Re: [Gnumed-bugs] [Gnumed-devel] database version requirement switch: 9.1, was: Problem in git bootstrapping v18 to v19 db
Date: Wed, 17 Jul 2013 23:39:37 +0200
User-agent: Mutt/1.5.21 (2010-09-15)

On Wed, Jul 17, 2013 at 09:18:20PM +0000, Jim Busser wrote:

> 1. If at http://www.enterprisedb.com/products-services-training/pgdownload
> 
>       9.2 is available
> 
> is there a preference that users *not* use 9.2, or does it likely not matter?

No, by all means go for 9.2 if that's possible. I've been
using 9.2 nearly since release.

> However is my safety net to ensure that I have backed up my
> 
>       
> backup-gnumed_v18-GNUmed_Team-MacBook-2.local-2013-07-17-13-48-15-database.sql
>       
> backup-gnumed_v18-GNUmed_Team-MacBook-2.local-2013-07-17-13-48-15-roles.sql

Absolutely. I would have several copies thereof on several
machines (spindles). The compress very well. And copy, too.

> and if I should migrate to a VM are these .sql files my
> means to import my data into a new pg?

Yes. Which I would test, test, and test again before
actually going live with the switch.

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.

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]