Re: [NOVICE] encoding problems

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Cliff Nieuwenhuis <cliff(at)nieusite(dot)com>
Cc: pgsql-novice(at)postgresql(dot)org, pgsql-hackers(at)postgresql(dot)org
Subject: Re: [NOVICE] encoding problems
Date: 2008-03-11 16:41:35
Message-ID: 23804.1205253695@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers pgsql-novice pgsql-patches

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

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Bruce Momjian 2008-03-11 17:03:19 Re: Autovacuum vs statement_timeout
Previous Message Zdenek Kotala 2008-03-11 16:41:07 Re: [PATCHES] Fix for large file support (nonsegment mode support)

Browse pgsql-novice by date

  From Date Subject
Next Message Joshua 2008-03-11 17:25:54 simple question concerning plpgsql and SQL Functions
Previous Message Cliff Nieuwenhuis 2008-03-11 15:10:15 encoding problems

Browse pgsql-patches by date

  From Date Subject
Next Message Zdenek Kotala 2008-03-11 17:07:21 Re: Remove FATAL from pg_lzdecompress
Previous Message Zdenek Kotala 2008-03-11 16:41:07 Re: [PATCHES] Fix for large file support (nonsegment mode support)