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
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers pgsql-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

Browse pgsql-hackers by date

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

Browse pgsql-patches by date

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