Re: [NOVICE] encoding problems

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

Martijn van Oosterhout <kleptog(at)svana(dot)org> writes:
> The other alternative is to convert tabs to spaces on output. Can't
> remember why we didn't do that.

Yeah. The idea I had was to invent a parameter specifying the number of
spaces a tab should expand to --- setting this to zero would give you
the current \x09 behavior. I'm not sure how painful it would be to
expand tabs properly in mbprint, but it seems possible.

regards, tom lane

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Magnus Hagander 2008-03-12 14:53:07 TODO-list on wiki (was: TODO update about SQLSTATE to PGconn)
Previous Message Bruce Momjian 2008-03-12 14:27:06 Re: Re: [COMMITTERS] pgsql: Add: > o Add SQLSTATE severit yto PGconn return status > >

Browse pgsql-novice by date

  From Date Subject
Next Message Tom Lane 2008-03-12 14:55:35 Re: [HACKERS] encoding problems
Previous Message Cliff Nieuwenhuis 2008-03-12 14:21:27 Re: [HACKERS] encoding problems

Browse pgsql-patches by date

  From Date Subject
Next Message Pavan Deolasee 2008-03-12 15:47:20 Re: [PERFORM] Very slow (2 tuples/second) sequential scan after bulk insert; speed returns to ~500 tuples/second after commit
Previous Message Heikki Linnakangas 2008-03-12 13:43:46 Re: [PERFORM] Very slow (2 tuples/second) sequential scan after bulk insert; speed returns to ~500 tuples/second after commit