Re: best practice in upgrading db structure - Mailing list pgsql-general

From Jim C. Nasby
Subject Re: best practice in upgrading db structure
Date
Msg-id 20060328221109.GC75181@pervasive.com
Whole thread Raw
In response to best practice in upgrading db structure  (SunWuKung <Balazs.Klein@axelero.hu>)
List pgsql-general
On Tue, Mar 28, 2006 at 09:28:12PM +0200, SunWuKung wrote:
> This is going to be an amateur question...
>
> Could somebody explain me, or point me to a resource where I can find
> out what is the recommended practice when a live db needs to be replaced
> with a new version of it that has a slightly different structure?
>
> My first guess would be to create the empty new version of the db and
> insert the data of the old one into it - adding and modifying it when
> necessary, but I am not sure.
>
> What do you usually do in a situation like this?

ALTER TABLE ...
--
Jim C. Nasby, Sr. Engineering Consultant      jnasby@pervasive.com
Pervasive Software      http://pervasive.com    work: 512-231-6117
vcard: http://jim.nasby.net/pervasive.vcf       cell: 512-569-9461

pgsql-general by date:

Previous
From: Tom Lane
Date:
Subject: Re: PostgreSQL support on Redhat Advance Server 2.1
Next
From: Tom Lane
Date:
Subject: Re: Auto convert for type?