Thu Sep 13 14:42:41 PDT 2007
- Previous message: [Slony1-general] cluster broken
- Next message: [Slony1-general] cluster broken
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
JP Fletcher <jpfletch at ca.afilias.info> writes: > Hi, > > My 1.2.11 cluster abruptly stopped working, with the following error > message present in the pg logs of the origin: > > 2007-09-13 20:29:06.358 UTC [1679750] cluster slony 10.1.2.133 ERROR: > syntax error at or near "order" at character 283 > 2007-09-13 20:29:06.358 UTC [1679750] cluster slony 10.1.2.133 > STATEMENT: declare LOG cursor for select log_origin, log_xid, > log_tableid, log_actionseq, log_cmdtype, > octet_length(log_cmddata), case when octet_length(log_cmddata) <= > 8192 then log_cmddata else null end from > "_cluster".sl_log_1 where log_origin = 8143 and ( order by > log_actionseq; > > > I had been changing some subscriptions around, with no evidence of > failure. Apart from that, the cluster wasn't doing anything... Hmm. This sounds a whole lot like: <http://gborg.postgresql.org/project/slony1/bugs/bugupdate.php?1226> That was supposedly fixed about two years ago. -- (reverse (concatenate 'string "ofni.secnanifxunil" "@" "enworbbc")) http://www3.sympatico.ca/cbbrowne/linuxxian.html There are three kinds of people: those who can count, and those who can't.
- Previous message: [Slony1-general] cluster broken
- Next message: [Slony1-general] cluster broken
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the Slony1-general mailing list