From: | "Jim C(dot) Nasby" <jnasby(at)pervasive(dot)com> |
---|---|
To: | SunWuKung <Balazs(dot)Klein(at)axelero(dot)hu> |
Cc: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: best practice in upgrading db structure |
Date: | 2006-03-28 22:11:10 |
Message-ID: | 20060328221109.GC75181@pervasive.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | 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(at)pervasive(dot)com
Pervasive Software http://pervasive.com work: 512-231-6117
vcard: http://jim.nasby.net/pervasive.vcf cell: 512-569-9461
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2006-03-28 22:13:33 | Re: Auto convert for type? |
Previous Message | Tom Lane | 2006-03-28 21:33:53 | Re: PostgreSQL support on Redhat Advance Server 2.1 |