Tom Lane wrote: > Dimitri Fontaine <dfonta...@hi-media.com> writes: > > So the case where pg_migrator still fails is when the .sql file of the > > module has changed in a way that restoring what pg_dump gives no longer > > match what the .so exposes, or if the new .so is non backward > > compatible? > > Exactly. And note that this is not pg_migrator's fault: a pg_dump > dump and reload of the database exposes the user to the same risks, > if the module author has not been careful about compatibility.
Agreed. In many ways pg_migrator failures will be caused by failures of the many tools it relies upon, as I mentioned a few days ago. -- 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
