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 9408C5E46D2 for ; Fri, 13 Aug 2004 09:38:10 -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 42956-10 for ; Fri, 13 Aug 2004 12:38:05 +0000 (GMT) Received: from laas.laas.fr (laas.laas.fr [140.93.0.15]) by svr1.postgresql.org (Postfix) with ESMTP id 3393A5E40BA for ; Fri, 13 Aug 2004 09:38:03 -0300 (ADT) Received: by laas.laas.fr (8.12.11/8.12.11) with SMTP id i7DCc7LC022513; Fri, 13 Aug 2004 14:38:08 +0200 (CEST) To: PostgreSQL Interfaces Subject: large object I/O seeing \\xxx encoding with v3 protocol From: Eric Marsden Organization: LAAS-CNRS http://www.laas.fr/ X-URL: http://www.chez.com/emarsden/ X-Message-Flags: Please don't feed the Microserfs X-Eric-Conspiracy: there is no conspiracy X-Attribution: ecm Date: Fri, 13 Aug 2004 14:38:07 +0200 Message-ID: User-Agent: Gnus/5.1006 (Gnus v5.10.6) Emacs/21.3 (gnu/linux) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii 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/12 X-Sequence-Number: 5060 Hi, 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.] I find this behaviour to be unfortunate, because it differs from the v2 protocol behaviour, and because I don't see any reason to encode the binary data in large objects. Was this change intentional? Thanks, -- Eric Marsden