Re: pg_migrator to /contrib in a later 9.0 beta

From: Bruce Momjian <bruce(at)momjian(dot)us>
To: Andrew Dunstan <andrew(at)dunslane(dot)net>
Cc: Robert Haas <robertmhaas(at)gmail(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(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 14:31:39
Message-ID: 201005021431.o42EVdj11080@momjian.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Andrew Dunstan wrote:
>
>
> Robert Haas wrote:
> > I don't think it's going
> > to be practical to retain all the migration code for every pair of
> > versions forever,
> >
>
> I thought the idea was just to support migration from version N to
> version N+1.

Oh, I will also support many older _source_ versions, like 8.3 and 8.4.
The question is whether a pg_migrator in /contrib should support
multiple _target_ versions.

(Again, I assumed this discussion would be necessary, and is best done
during beta.)

--
Bruce Momjian <bruce(at)momjian(dot)us> http://momjian.us
EnterpriseDB http://enterprisedb.com

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2010-05-02 14:34:43 Re: TOAST code ignores freespace (was Tweak TOAST code)
Previous Message Bruce Momjian 2010-05-02 14:30:00 Re: pg_migrator to /contrib in a later 9.0 beta