X-Original-To: pgsql-sql-postgresql.org@localhost.postgresql.org Received: from localhost (neptune.hub.org [200.46.204.2]) by svr1.postgresql.org (Postfix) with ESMTP id 142C0D1B477 for ; Sat, 20 Dec 2003 04:46:39 +0000 (GMT) Received: from svr1.postgresql.org ([200.46.204.71]) by localhost (neptune.hub.org [200.46.204.2]) (amavisd-new, port 10024) with ESMTP id 21402-10 for ; Sat, 20 Dec 2003 00:45:50 -0400 (AST) Received: from sss.pgh.pa.us (unknown [192.204.191.242]) by svr1.postgresql.org (Postfix) with ESMTP id BAA44D1B47C for ; Sat, 20 Dec 2003 00:45:49 -0400 (AST) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.12.10/8.12.10) with ESMTP id hBK4jl19014348; Fri, 19 Dec 2003 23:45:47 -0500 (EST) To: "Matt Van Mater" Cc: bruno@wolff.to, pgsql-sql@postgresql.org Subject: Re: how to preserve \n in select statement In-reply-to: References: Comments: In-reply-to "Matt Van Mater" message dated "Fri, 19 Dec 2003 23:23:26 -0500" Date: Fri, 19 Dec 2003 23:45:47 -0500 Message-ID: <14347.1071895547@sss.pgh.pa.us> From: Tom Lane X-Virus-Scanned: by amavisd-new at postgresql.org X-Archive-Number: 200312/136 X-Sequence-Number: 16302 "Matt Van Mater" writes: > I just don't see why pgsql can't return my data exactly as I entered > it. Because you are using an input syntax that requires that quotes and backslashes be escaped. There are other input methods available that don't require this, but they have disadvantages of their own. In particular, you have to separate data from SQL command if you want a no-escape-processing behavior for data. > I think this behavior stems from a security problem psql had a while > back where escape characters were being interpreted, and this may be > another instance of that functionality. Matt, you have no idea what you are talking about. regards, tom lane