Re: large object I/O seeing \\xxx encoding with v3

>>>>> "tl" == Tom Lane <tgl@sss.pgh.pa.us> writes:
 ecm> When using the v3 fe/be protocol, data read and written to large ecm> objects via the loread and lowrite
functionsseems to be \\xxx ecm> encoded, as per literal escaping or data for the BYTEA type. For ecm> instance,
newlineswritten using lowrite() are later received as ecm> \\012. 
 
 tl> It sounds to me like you have asked for textual rather than binary tl> results from loread.
 you're right; I am sending the type of the argument as 0, so it's text.
 It seems to me that it would be more useful, and more consistent with the way text is handled in the fe/be protocol,
touse the character encoding that was requested by the client (the equivalent of PQsetClientEncoding) instead of this
literal\xxx escaping. Would be a backwards-incompatible change, though.
 
  Thanks,   
-- 
Eric Marsden                          <URL:http://www.laas.fr/~emarsden/>