Tom Lane wrote: > Bruce Momjian <br...@momjian.us> writes: > > Tom Lane wrote: > >> There was just some discussion about that on postgis-devel. I think the > >> conclusion was that you would have to do the PostGIS update as a > >> separate step. They intend to support both 1.3.x and 1.4.x on current > >> versions of Postgres for some time, so in principle you could do it in > >> either order. > > > Oh, yea, you can't go from PostGIS version 1.3 to 1.4 _while_ you do the > > pg_migrator upgrade. It has to be done either before or after > > pg_migrator is run. I wonder how I could prevent someone from trying > > that trick. > > You don't need to, because it will fail automatically. They are using > version-numbered .so files, so C-language functions referencing the 1.3 > .so will fail to load if only the 1.4 .so is in the new installation.
Nice. Something to be learned there. ;-) -- 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
