Skip site navigation (1) Skip section navigation (2)

Re: Escape handling in COPY, strings, psql

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>
Cc: PostgreSQL-development <pgsql-hackers(at)postgreSQL(dot)org>,Sergey Ten <sergey(at)sourcelabs(dot)com>,"'Christopher Kings-Lynne'" <chriskl(at)familyhealth(dot)com(dot)au>,jason(at)sourcelabs(dot)com
Subject: Re: Escape handling in COPY, strings, psql
Date: 2005-05-29 15:15:49
Message-ID: 3945.1117379749@sss.pgh.pa.us (view raw or flat)
Thread:
Lists: pgsql-hackerspgsql-patches
Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> writes:
> One other idea would be to remove escape processing for single-quoted
> strings but keep it for our $$ strings, becuase they are not ANSI
> standard.

There is *no* escape processing within $$, and never will be, because
that would destroy the entire point.  You'd be right back having to
double backslashes.

			regards, tom lane

In response to

pgsql-hackers by date

Next:From: Tom LaneDate: 2005-05-29 15:18:40
Subject: Re: Inefficiency in recent pgtz patch
Previous:From: Hannu KrosingDate: 2005-05-29 14:49:23
Subject: Re: compiling postgres with Visual Age compiler on

pgsql-patches by date

Next:From: Michael FuhrDate: 2005-05-29 15:19:54
Subject: pg_buffercache causes assertion failure
Previous:From: Bruce MomjianDate: 2005-05-29 13:30:06
Subject: Re: Escape handling in COPY, strings, psql

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group