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.
---------------------------(end of broadcast)---------------------------
TIP 6: Have you searched our list archives?
http://archives.postgresql.org
