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

Adding \x escape processing to COPY, psql, backend

From: Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>
To: Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>
Cc: Sergey Ten <sergey(at)sourcelabs(dot)com>,"'Christopher Kings-Lynne'" <chriskl(at)familyhealth(dot)com(dot)au>,jason(at)sourcelabs(dot)com,PostgreSQL-patches <pgsql-patches(at)postgresql(dot)org>
Subject: Adding \x escape processing to COPY, psql, backend
Date: 2005-05-30 19:33:38
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-hackerspgsql-patches
Bruce Momjian wrote:
> Here is an updated version of the COPY \x patch.  It is the first patch
> attached.
> Also, I realized that if we support \x in COPY, we should also support
> \x in strings to the backend.  This is the second patch.

Here is a new version of the three \x hex support patches.  I have added
\x for psql variables, which is the last patch.

I have IM'ed with Peter and he is now OK with the idea of supporting \x,
with the underestanding that it doesn't take us any farther away from
compatibility than we are now.

I have already fixed the psql octal/decimal/hex behavior in another

  Bruce Momjian                        |
  pgman(at)candle(dot)pha(dot)pa(dot)us               |  (610) 359-1001
  +  If your life is a hard drive,     |  13 Roberts Road
  +  Christ can be your backup.        |  Newtown Square, Pennsylvania 19073

In response to


pgsql-hackers by date

Next:From: Tom LaneDate: 2005-05-30 19:41:19
Subject: Re: Adding \x escape processing to COPY, psql, backend
Previous:From: Robert BernierDate: 2005-05-30 18:42:32
Subject: Re: US Goverment and Patents

pgsql-patches by date

Next:From: Bruce MomjianDate: 2005-05-30 19:38:03
Subject: Re: [ADMIN] Config option log_statement
Previous:From: Bruce MomjianDate: 2005-05-30 18:30:54
Subject: Support only octal for psql PROMPT % values

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