Wed Oct 21 08:25:42 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 ]
Quoting Glyn Astill <glynastill at yahoo.co.uk>: >> That's working and committed to 2.0 + HEAD. >> > > That's cool, just a note that I was upgrading to 1.2.17 when I got > this, not 2.0.x Uh, oh... That means I need to fix 1.2.17, presumably rolling 1.2.18. And I need to think about that a little further; "DROP FUNCTION IF EXISTS" wasn't introduced until, I believe, PostgreSQL 8.2. (It's not in 8.1.) So that strategy won't work for 1.2 :-(. Thanks for letting me know!
- 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