| 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-12 20:53:34 |
| Message-ID: | dcc563d10812121253w1e116cc3tea801b7ebf60d636@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Fri, Dec 12, 2008 at 1:51 PM, Thom Brown <thombrown(at)gmail(dot)com> wrote:
> What about managing the script files themselves, keeping in mind that some
> scripts could be applied to more than one database version, like a database
> which is a branched version of another database, but which have common
> elements which can both be updated by a common script. Although sometimes a
> script would be unique to that database.
I'd use a branched svn / cvs type setup. And upgrade scripts that
take you from branch to another (or trunk to a new branch, whichever
you'd be doing.)
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2008-12-12 21:48:07 | Re: pg_stat_reset not resetting all stats |
| Previous Message | Thom Brown | 2008-12-12 20:51:28 | Re: Database config managment |