On Wed, 2006-11-08 at 07:00 -0800, Darcy Buskermolen wrote:
> On Tuesday 07 November 2006 15:03, Jeff Davis wrote:
> > 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?
> 
> We could take the same approach with this as we did with standards conformant 
> strings, which is we set the guc's on the sesssions between the nodes.  Would 
> that fix your issue?
> 

Is it possible to get this change in before the release of 1.2.1? I
attached a quick patch.

Regards,
	Jeff Davis

-------------- next part --------------
A non-text attachment was scrubbed...
Name: slony.patch
Type: text/x-patch
Size: 662 bytes
Desc: not available
Url : http://gborg.postgresql.org/pipermail/slony1-general/attachments/20061113/56cd63b9/attachment.bin