Wed Dec 9 09:58:57 PST 2009
- Previous message: [Slony1-general] PGRES_FATAL_ERROR ERROR: cannot change return type of existing function
- Next message: [Slony1-general] Data Changes Via Slonik
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
On 12/8/2009 2:24 PM, Joseph S wrote: > I used this and was able to upgrade from 1.2.15 to 1.2.18, but I did get > this warning: > > <stdin>:14: Possible unsupported PostgreSQL version 8.3, defaulting to > 8.1 support > > I'm assuming for that I can ignore this. Yes, but unfortunately I just found and fixed a bug in that drop_if_exists function. Chris will be rolling a 1.2.19 today. Jan > > Vick Khera wrote: >> On Thu, Dec 3, 2009 at 5:15 AM, Glyn Astill <glynastill at yahoo.co.uk> wrote: >> >>> I took a quick peek in slony1_funcs.sql from the 1.2.18 release and the drop_if_exists functionality appears to be in there (although not in the slony1_funcs.vNN.sql scripts). I'm going to do a few more tests before upgrading our servers... >>> >>> >> >> Once I added the lines >> >> drop function if exists @NAMESPACE at .ddlScript_complete (int4, text, int4); >> drop function if exists @NAMESPACE at .updateReloid (int4, int4); >> >> to slony1_funcs.sql it as was installed, my update succeeded. >> > _______________________________________________ > Slony1-general mailing list > Slony1-general at lists.slony.info > http://lists.slony.info/mailman/listinfo/slony1-general -- Anyone who trades liberty for security deserves neither liberty nor security. -- Benjamin Franklin
- Previous message: [Slony1-general] PGRES_FATAL_ERROR ERROR: cannot change return type of existing function
- Next message: [Slony1-general] Data Changes Via Slonik
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the Slony1-general mailing list