| From: | "Kevin Grittner" <Kevin(dot)Grittner(at)wicourts(dot)gov> |
|---|---|
| To: | "daveg" <daveg(at)sonic(dot)net>,"Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | "Alvaro Herrera" <alvherre(at)commandprompt(dot)com>, "Andrew Dunstan" <andrew(at)dunslane(dot)net>, "David Fetter" <david(at)fetter(dot)org>, "Peter Eisentraut" <peter_e(at)gmx(dot)net>, "Bruce Momjian" <bruce(at)momjian(dot)us>, <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Alpha releases: How to tag |
| Date: | 2009-08-10 15:41:14 |
| Message-ID: | 4A7FF94A0200002500029707@gw.wicourts.gov |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
daveg <daveg(at)sonic(dot)net> wrote:
> When I was at Sybase, changes to the on disk structure were required
> to provide code to do the migration. Nonetheless, at release time,
> the migrate process was almost always discovered to be broken,
> sometimes even before it was shipped to customers.
As a long-time user of Sybase SQL Server and it's later incarnation as
Adaptive Server Enterprise, I can confirm that the result of this
approach was often unsatisfactory from a user perspective. That is,
the discovery was not always made before shipping to customers. :-(
I have high hopes for pg_migrator, but the pg_dump | psql approach has
always worked well for us -- no surprises and no pain beyond the
resource management issues.
-Kevin
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bruce Momjian | 2009-08-10 15:43:26 | Re: Shipping documentation untarred |
| Previous Message | Tom Lane | 2009-08-10 15:36:36 | Re: GRANT ON ALL IN schema |