| From: | John DeSoi <desoi(at)pgedit(dot)com> |
|---|---|
| To: | Bradley Holbrook <operations_bradley(at)servillian(dot)ca> |
| Cc: | "'Scott Marlowe'" <scott(dot)marlowe(at)gmail(dot)com>, "'French, Martin'" <frenchm(at)cromwell(dot)co(dot)uk>, <pgsql-admin(at)postgresql(dot)org> |
| Subject: | Re: Postgres Backup Utility |
| Date: | 2011-01-21 01:08:42 |
| Message-ID: | B51575A9-7BA1-4ADD-B152-38B32CD0C015@pgedit.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-admin |
On Jan 20, 2011, at 12:42 PM, Bradley Holbrook wrote:
> Our developers never decide what goes to where... they just happily plumb
> away on the development db until we're ready to take our product to testing
> (at regular intervals), once QA is passed, we wish to apply these to live.
> We have several diff tools and sync tools, but they take forever (especially
> the ones that only go one schema at a time).
Using a diff tool, how would you know if a column was dropped and another one added versus simply renaming a column? Won't that kind of difference matter when you want to apply the changes to your production database?
John DeSoi, Ph.D.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Scott Marlowe | 2011-01-21 01:44:43 | Re: Postgres Backup Utility |
| Previous Message | Bruce Momjian | 2011-01-21 00:14:57 | Re: plpyhton |