Robert Haas wrote:
> On Aug 7, 2009, at 11:50 PM, Bruce Momjian <bruce@momjian.us> wrote:
>
> > David Fetter wrote:
> >>> Odds are that the patch submitters will not understand enough to
> >>> know how to modify pg_migrator, but just knowing something broke is
> >>> usually enough for the hackers group to find a fix.
> >>
> >> This is a pretty serious drawback. If we're going to require that
> >> people send migration scripts when they change the on-disk format,
> >> this needs to be easy. The program, whatever it turns out to be,
> >> needs to take composable changes which people would submit along with
> >> their patch, just as they do docs.
> >>
> >> How much refactoring of pg_migrator would such a change take? Would
> >> it be worthwhile to do that, or just start a different project?
> >
> > I have no idea what you are thinking. pg_migrator is in C just like
> > the
> > backend code. Do you want some plugin module to do migrations? I
> > have
> > neither the time or desire to implement that.
>
> It seems that it would also negate one of the major benefits of
> pg_migrator, which is that it doesn't require you to rewrite all of
> your data.
I don't understand how this relates to rewriting data. David was asking
if we should require patch submitters to update pg_migrator. If they
can do that, great, but if not, we can figure out an approach for them.
-- Bruce Momjian <bruce@momjian.us> http://momjian.us EnterpriseDB
http://enterprisedb.com
+ If your life is a hard drive, Christ can be your backup. +
