X-Original-To: pgsql-interfaces-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [200.46.204.144]) by svr1.postgresql.org (Postfix) with ESMTP id 7C3F65E46D3 for ; Fri, 13 Aug 2004 11:10:11 -0300 (ADT) Received: from svr1.postgresql.org ([200.46.204.71]) by localhost (av.hub.org [200.46.204.144]) (amavisd-new, port 10024) with ESMTP id 71377-01 for ; Fri, 13 Aug 2004 14:10:11 +0000 (GMT) Received: from sss.pgh.pa.us (sss.pgh.pa.us [66.207.139.130]) by svr1.postgresql.org (Postfix) with ESMTP id A32A95E46D2 for ; Fri, 13 Aug 2004 11:10:08 -0300 (ADT) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.12.11/8.12.11) with ESMTP id i7DEA7w6022988; Fri, 13 Aug 2004 10:10:07 -0400 (EDT) To: Eric Marsden Cc: PostgreSQL Interfaces Subject: Re: large object I/O seeing \\xxx encoding with v3 protocol In-reply-to: References: Comments: In-reply-to Eric Marsden message dated "Fri, 13 Aug 2004 14:38:07 +0200" Date: Fri, 13 Aug 2004 10:10:06 -0400 Message-ID: <22987.1092406206@sss.pgh.pa.us> From: Tom Lane X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, hits=0.0 tagged_above=0.0 required=5.0 tests= X-Spam-Level: X-Archive-Number: 200408/13 X-Sequence-Number: 5061 Eric Marsden writes: > When using the v3 fe/be protocol, data read and written to large > objects via the loread and lowrite functions seems to be \\xxx > encoded, as per literal escaping or data for the BYTEA type. For > instance, newlines written using lowrite() are later received as > \\012. > [I am seeing this with my own implementation of the fe/be protocol; > I'm not using libpq.] It sounds to me like you have asked for textual rather than binary results from loread. regards, tom lane