Mon Oct 19 08:11:29 PDT 2009
- Previous message: [Slony1-general] PGRES_FATAL_ERROR ERROR: cannot change return type of existing function
- Next message: [Slony1-general] PGRES_FATAL_ERROR ERROR: cannot change return type of existing function
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
--- On Mon, 19/10/09, Glyn Astill <glynastill at yahoo.co.uk> wrote: > > --- On Mon, 19/10/09, Glyn Astill <glynastill at yahoo.co.uk> > wrote: > > Hi chaps, > > > > Is anyone else seeing this when doing UPGRADE > > FUNCTIONS? I'm guessing it's the recent int / > bigint > > changes? > > > > And I'm getting: > > > > glyn at Way5d:/pgsql/slony$ slonik upgrade_functions.scr > > upgrade_functions.scr:9: Possible unsupported > PostgreSQL > > version 8.3, defaulting to 8.1 support > > upgrade_functions.scr:9: loading of file > > /usr/local/pgsql/share//slony1_funcs.sql: > PGRES_FATAL_ERROR > > ERROR: cannot change return type of existing > function > > HINT: Use DROP FUNCTION first. > > ERROR: cannot change return type of existing > > function > > HINT: Use DROP FUNCTION first. > > > I bumbled around it with the following on each node: > > psql -U slony -d SEE -c 'drop function > _main_replication_test.ddlscript_complete(integer, text, > integer)' > psql -U slony -d SEE -c 'drop function > _main_replication_test.updatereloid(integer, integer)' > sed -e > 's/@NAMESPACE@/_main_replication_test/g;s/@MODULEVERSION@/1.2.17/g' > slony1_funcs.sql | psql -U slony -d SEE > Actually : sed -e 's/@NAMESPACE@/_main_replication_test/g;s/@MODULEVERSION@/1.2.17/g;s/@CLUSTERNAME@/main_replication_test/g' slony1_funcs.sql | psql -U slony -d SEE Glyn
- Previous message: [Slony1-general] PGRES_FATAL_ERROR ERROR: cannot change return type of existing function
- Next message: [Slony1-general] PGRES_FATAL_ERROR ERROR: cannot change return type of existing function
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the Slony1-general mailing list