| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Robert Haas <robertmhaas(at)gmail(dot)com> |
| Cc: | Andrew Dunstan <andrew(at)dunslane(dot)net>, Bruce Momjian <bruce(at)momjian(dot)us>, Magnus Hagander <magnus(at)hagander(dot)net>, Dimitri Fontaine <dfontaine(at)hi-media(dot)com>, Peter Eisentraut <peter_e(at)gmx(dot)net>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: pg_migrator to /contrib in a later 9.0 beta |
| Date: | 2010-05-02 03:52:52 |
| Message-ID: | 865.1272772372@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Robert Haas <robertmhaas(at)gmail(dot)com> writes:
> On Sat, May 1, 2010 at 11:38 PM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
>> To the extent that future bug fixes are relevant to multiple versions
>> of pg_migrator, we could just apply them to multiple branches, same as
>> we manage such fixes for the core code. I don't see that trying to
>> have a single version of pg_migrator is going to make things easier
>> anywhere.
> That might be OK if by "multiple versions" we mean "multiple branches
> within the repository". But I'm not so sure about having a version in
> the core repository and another version on pgfoundry, or something of
> that sort.
True. If we push it into contrib as of 9.0, I think this won't be too
bad, because the pgfoundry version will only be covering 8.3->8.4.
Given all the limitations in that version, it's not going to be too
interesting and will probably die on the vine pretty quickly. If we
hold off merging it till 9.1, though, the pgfoundry version probably
will be useful and in need of maintenance for a while to come.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Peter Eisentraut | 2010-05-02 10:22:47 | Re: pg_migrator to /contrib in a later 9.0 beta |
| Previous Message | Robert Haas | 2010-05-02 03:40:09 | Re: pg_migrator to /contrib in a later 9.0 beta |