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 E3A1E14B281C for ; Wed, 11 Aug 2004 11:20:41 -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 06252-07 for ; Wed, 11 Aug 2004 14:20:38 +0000 (GMT) Received: from main.gmane.org (main.gmane.org [80.91.224.249]) by svr1.postgresql.org (Postfix) with ESMTP id 95C1114B280B for ; Wed, 11 Aug 2004 11:20:34 -0300 (ADT) Received: from root by main.gmane.org with local (Exim 3.35 #1 (Debian)) id 1Buty2-0006tm-00 for ; Wed, 11 Aug 2004 16:20:38 +0200 Received: from melbourne.laas.fr ([140.93.21.103]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Wed, 11 Aug 2004 16:20:38 +0200 Received: from emarsden by melbourne.laas.fr with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Wed, 11 Aug 2004 16:20:38 +0200 X-Injected-Via-Gmane: http://gmane.org/ To: pgsql-interfaces@postgresql.org From: Eric Marsden Subject: Large object reads/writes undergoing \\xxx escaping Date: Wed, 11 Aug 2004 16:00:53 +0200 Organization: LAAS-CNRS http://www.laas.fr/ Lines: 16 Message-ID: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Complaints-To: usenet@sea.gmane.org X-Gmane-NNTP-Posting-Host: melbourne.laas.fr X-URL: http://www.chez.com/emarsden/ X-Message-Flags: Don't Panic! X-Eric-Conspiracy: there is no conspiracy X-Attribution: ecm User-Agent: Gnus/5.1006 (Gnus v5.10.6) Emacs/21.3 (gnu/linux) Cancel-Lock: sha1:KVyR1ivLsH6x5zHff7+L2Dmj4BE= 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/17 X-Sequence-Number: 5065 Hi, With recent PostgreSQL versions, I/O on large objects (via the internal functions loread and lowrite) suffers \\xxx escaping, as per the BYTEA type. For instance, newlines in the data passed to lowrite are later read via loread as \\012. I find this to be annoying (I don't see any reason for large object data to go through any encoding whatsoever), and it doesn't seem to be documented. Is it the intended behaviour? [I am not using libpq; I see this using my own fe/be protocol implementation.] -- Eric Marsden