From: | Jeff Amiel <jamiel(at)istreamimaging(dot)com> |
---|---|
To: | pgsql-general(at)postgresql(dot)org |
Subject: | Schema comparison tool |
Date: | 2005-02-15 15:01:29 |
Message-ID: | 42120EC9.3040702@istreamimaging.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
I'm looking specifically for a tool to help compare 2 database schemas
(nominally, production and development) and generate the appropriate SQL
(that can be later executed) to bring the to schema's into sync.
Option1 :
pg_dump -s firstdatabasename > first
pg_dump -s seconddatabasename > second
diff first second
(obviously wont generate SQL to remedy the differences)
Option2:
pgdiff (http://gborg.postgresql.org/project/pgdiff/projdisplay.php)
(old abandoned perl project that doesn't work...)
Option 3:
pgdiff (http://gborg.postgresql.org/project/pgdiff/projdisplay.php)
(old abandoned TCL project which requires AOLServer to run???)
Option 4:
EMS PostgreSQL DB Comparer
(http://www.sqlmanager.net/products/postgresql/dbcomparer)
Slick tool...fairly cheap ($69)...doesnt let you exclude certain
specific tables/sequences/databases, but otherwise, pretty functional.
What does the rest of the postgreSQL admin community do in order to
"bring-live" database schema changes from their development environment
to production? Are there other options/techniques out there?
Any help would be appreciated.
Jeff
From | Date | Subject | |
---|---|---|---|
Next Message | rwhart | 2005-02-15 15:16:13 | Alternate db location |
Previous Message | Shridhar Daithankar | 2005-02-15 15:00:23 | Re: Trading off large objects (arrays, large strings, large tables) for timeseries |