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

Re: [HACKERS] backslash in psql output

From: Bruce Momjian <maillist(at)candle(dot)pha(dot)pa(dot)us>
To: lockhart(at)alumni(dot)caltech(dot)edu (Thomas G(dot) Lockhart)
Cc: hackers(at)postgreSQL(dot)org
Subject: Re: [HACKERS] backslash in psql output
Date: 1998-10-10 03:04:13
Message-ID: 199810100304.XAA13940@candle.pha.pa.us (view raw or flat)
Thread:
Lists: pgsql-hackers
> > now the format will be ambigious.
> >         test=> insert into test3 values ('\\x');
> >         test=> select * from test3;
> >         --
> >         \x
> > This used to show as:
> >         --
> >         \\x
> > Comments?
> 
> Well, actually I've been thinking that this is closer to the behavior we
> might want (though I haven't looked carefully at the new version). Of
> course it bothered me more than it should have, since I misunderstood
> where the re-escaping was happening; I had thought it was happening in
> the backend.
> 
> psql could have an option to re-escape strings, but imho by default
> should display what is stored, not what was typed in originally.
> 
> pg_dump _should_ re-escape everything, so that it reloads properly.

But what about backward compatability?  Aren't there people expecting
psql output to show double backslashes?  What do we do to display pipes
in the output?

-- 
  Bruce Momjian                        |  http://www.op.net/~candle
  maillist(at)candle(dot)pha(dot)pa(dot)us            |  (610) 853-3000
  +  If your life is a hard drive,     |  830 Blythe Avenue
  +  Christ can be your backup.        |  Drexel Hill, Pennsylvania 19026


In response to

Responses

pgsql-hackers by date

Next:From: Bruce MomjianDate: 1998-10-10 03:08:01
Subject: Re: [HACKERS] dynamic libraries
Previous:From: Thomas G. LockhartDate: 1998-10-10 02:31:07
Subject: Re: [HACKERS] backslash in psql output

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