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 7C9A85E37D0 for ; Fri, 13 Aug 2004 14:49:54 -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 28686-08 for ; Fri, 13 Aug 2004 17:49:52 +0000 (GMT) Received: from sss.pgh.pa.us (sss.pgh.pa.us [66.207.139.130]) by svr1.postgresql.org (Postfix) with ESMTP id B4A275E46D8 for ; Fri, 13 Aug 2004 14:49:51 -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 i7DHnnRo025125; Fri, 13 Aug 2004 13:49:49 -0400 (EDT) To: Eric Marsden Cc: PostgreSQL Interfaces Subject: Re: large object I/O seeing \\xxx encoding with v3 protocol In-reply-to: References: <22987.1092406206@sss.pgh.pa.us> Comments: In-reply-to Eric Marsden message dated "Fri, 13 Aug 2004 17:39:21 +0200" Date: Fri, 13 Aug 2004 13:49:49 -0400 Message-ID: <25124.1092419389@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/15 X-Sequence-Number: 5063 Eric Marsden writes: > It seems to me that it would be more useful, and more consistent > with the way text is handled in the fe/be protocol, to use the > character encoding that was requested by the client (the equivalent > of PQsetClientEncoding) instead of this literal \xxx escaping. Surely not. This is bytea data we are talking about --- there is no reason to suppose that encoding has anything to do with it. If you want client_encoding to take a hand, you should be storing data as text not bytea. regards, tom lane