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. -- Bruce Momjian <br...@momjian.us> http://momjian.us EnterpriseDB http://enterprisedb.com + If your life is a hard drive, Christ can be your backup. + -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
