On Tuesday 11 March 2008 11:41:35 Tom Lane wrote:
> Cliff Nieuwenhuis <cliff(at)nieusite(dot)com> writes:
> > I'm not sure how to ask this question. I have written a function, and
> > with PostgreSQL 8.0.13 I can do a "\df+" and see something like this
> > under Source Code:
> > DECLARE
> > result text;
> > ...
> > If I create the same function on my computer running PostgreSQL 8.3.0 and
> > try the \df+ then the Source Code shows:
> > \x09DECLARE
> > \x09\x09result text;
> > ...
> That's not an encoding problem, that's an intentional behavioral change
> in the way that psql formats strings for display.
> I guess it's a bit annoying if you were hoping that tabs would be useful
> for pretty-printing purposes. Should we reconsider what's done with a
> tab in mbprint.c?
> regards, tom lane
My vote would be to go back to the old way, or at least have that as an option
of some sort. I use command-line psql all the time -- to me, psql offers the
same advantages as using a command-line interface for other work. I find the
extra characters really get in the way.
Thanks for the prompt reply!
In response to
pgsql-novice by date
|Next:||From: Martijn van Oosterhout||Date: 2008-03-12 08:16:27|
|Subject: Re: [NOVICE] encoding problems|
|Previous:||From: Joshua||Date: 2008-03-11 17:25:54|
|Subject: simple question concerning plpgsql and SQL Functions|
pgsql-hackers by date
|Next:||From: Bruce Momjian||Date: 2008-03-11 19:45:01|
|Subject: Re: What is the maximum encoding-conversion growth
|Previous:||From: Bruce Momjian||Date: 2008-03-11 18:15:05|
|Subject: Re: Planning large IN lists|
pgsql-patches by date
|Next:||From: Tom Lane||Date: 2008-03-11 19:11:09|
|Subject: Re: TransactionIdIsInProgress() cache |
|Previous:||From: Joshua D. Drake||Date: 2008-03-11 18:07:27|
|Subject: Re: Patch for Prevent pg_dump/pg_restore from being
affected by statement_timeout|