| From: | Josh Berkus <josh(at)agliodbs(dot)com> |
|---|---|
| To: | pgsql-hackers(at)postgresql(dot)org |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Andrew Dunstan <andrew(at)dunslane(dot)net>, David Fetter <david(at)fetter(dot)org>, Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>, PostgreSQL advocacy <pgsql-advocacy(at)postgresql(dot)org> |
| Subject: | Re: [HACKERS] PGUpgrade WAS: Audio interview |
| Date: | 2006-02-08 20:57:07 |
| Message-ID: | 200602081257.08074.josh@agliodbs.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-advocacy pgsql-hackers |
Tom,
> If such a tool were available, I don't think it'd be hard to get
> consensus on organizing our releases so that it were applicable more
> often than not. We could postpone changes that would affect user
> table contents until we'd built up a backlog that would all go into
> one release. Even a minimal commitment in that line would probably
> result in pgupgrade working for at least every other release, and
> that would be enough to make it worthwhile if you ask me ...
We could even make that our first/second dot difference in the future.
That is, 8.2 will be pg-upgradable from 8.1 but 9.0 will not.
--
--Josh
Josh Berkus
Aglio Database Solutions
San Francisco
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Hannu Krosing | 2006-02-08 20:58:53 | Re: [HACKERS] PGUpgrade WAS: Audio interview |
| Previous Message | Tom Lane | 2006-02-08 20:51:08 | Re: [HACKERS] PGUpgrade WAS: Audio interview |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Hannu Krosing | 2006-02-08 20:58:53 | Re: [HACKERS] PGUpgrade WAS: Audio interview |
| Previous Message | Tom Lane | 2006-02-08 20:51:08 | Re: [HACKERS] PGUpgrade WAS: Audio interview |