I run slony and have escape_string_warning = on. Is there any interest
in preventing slony from using queries that cause that warning?
We could either detect backends >= 8.1 and use E'' strings, or use
PQexecParams instead.
Is there a reason that's not done? If I wrote such a patch, would it be
accepted, or would it be needless code complexity?
Regards,
Jeff Davis
_______________________________________________
Slony1-general mailing list
[email protected]
http://gborg.postgresql.org/mailman/listinfo/slony1-general
