b***@mnogosearch.org
2013-03-01 05:38:42 UTC
Author: Alexander Barkov
From ChangeLog:
Improved compatibility with the latest versions of PostgreSQL. Escaping of the SQL character literals for PostgreSQL >= 90000 was changed from the C-alike stype (using backslash) to the standard SQL style.
Please upgrade.
Thanks.
Reply: <http://www.mnogosearch.org/board/message.php?id=21513>
It seems that postgresql has changed the way they handle escape characters. When setting 'standard_conforming_strings = off' in postgresql.conf the error is gone and indexer seem to finish successfully.
For more see http://www.postgresql.org/docs/9.1/static/sql-syntax-lexical.html.
This problem was fixed in 3.3.13.For more see http://www.postgresql.org/docs/9.1/static/sql-syntax-lexical.html.
From ChangeLog:
Improved compatibility with the latest versions of PostgreSQL. Escaping of the SQL character literals for PostgreSQL >= 90000 was changed from the C-alike stype (using backslash) to the standard SQL style.
Please upgrade.
Unfortunatly search.cgi crashes.
Can you please provide more information?Thanks.
Reply: <http://www.mnogosearch.org/board/message.php?id=21513>