Tue Oct 1 13:06:01 PDT 2013
- Previous message: [Slony1-general] help with error
- Next message: [Slony1-general] MAXSTATEMENTS in src/parsestatements
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Hmm, ok. We are migrating, however slowly, to postgresql 9.2 and the corresponding slony1 package in the pgdg apt-get repo. I inherited this dinosaur :) Thanks for the quick response. Mike On 10/1/13 3:58 PM, "Steve Singer" <steve at ssinger.info> wrote: >On 10/01/2013 03:47 PM, Mike James wrote: >> I just noticed this error in the pg log files. This particular old >> instance is running postgresql 8.3.9 and slony1 2.0.3 rc2. Any ideas >> where this error originates. Google wasn't helpful in this case. Can I >> ignore it? >> >> function _snapcluster.shouldslonyvacuumtable(name, name) does not exist >> at character 9 >> > >This bug was fixed between 2.0.3 RC2 and the actual 2.0.3 >(e31daffec5968470072a1dd435e11d49e620111c I think) > >Note that 2.0.3 ended up being a bad release, if your upgrading you >should at *least* upgrade to 2.0.4 > > >> Mike >> >> >> _______________________________________________ >> Slony1-general mailing list >> Slony1-general at lists.slony.info >> http://lists.slony.info/mailman/listinfo/slony1-general >> >
- Previous message: [Slony1-general] help with error
- Next message: [Slony1-general] MAXSTATEMENTS in src/parsestatements
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the Slony1-general mailing list