Re: Database config managment

From: "Scott Marlowe" <scott(dot)marlowe(at)gmail(dot)com>
To: "Thom Brown" <thombrown(at)gmail(dot)com>
Cc: pgsql-general(at)postgresql(dot)org
Subject: Re: Database config managment
Date: 2008-12-11 17:17:40
Message-ID: dcc563d10812110917u10601d32n892fdc2138e651fa@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On Thu, Dec 11, 2008 at 5:30 AM, Thom Brown <thombrown(at)gmail(dot)com> wrote:
> What do you folk think is the best way to manage deployments to databases?
> This would include things like table/view/function creations/changes and
> possibly static data changes.

The easiest way I've found to do it is to create a changetrack table
in pgsql, and then make each update use that. You can get fancy if
you want, or just keep it simple. For instance:

create table chtrack (id int primary key, changename text, changedesc text);

Then in a file you can have:

begin;
insert into chtrack (id, changename, changedesc) Values (10,'schema
create','This change creates the initial db schema');
create table
etc...
commit;

If any of the script fails, the whole thing does and your db doesn't
change. Then you can create your new updates in a similar manner.

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Simon Riggs 2008-12-11 17:37:10 Re: Data Replication
Previous Message Joshua D. Drake 2008-12-11 17:14:45 Re: Data Replication