source control integration - Mailing list pgsql-general

From Simon Wittber
Subject source control integration
Date
Msg-id 4e4a11f8041205165759a78641@mail.gmail.com
Whole thread Raw
Responses Re: source control integration  (Greg Stark <gsstark@mit.edu>)
List pgsql-general
What is currently regarded as postgresql best-practice for controlling
changes to a database?

I currently administer SQL Server. I implemented a system which
scripts every database object each hour (into a SQL script on the
filesystem), and then uses SVN to track changes and email me if a
change has occured, which then gives me the opportunity to review and
commit the change.

Is this sort of thing possible with postgresql?

Sw.

pgsql-general by date:

Previous
From: Doug McNaught
Date:
Subject: Re: SSL confirmation
Next
From: Michael Fuhr
Date:
Subject: Re: Function Problem