From: | "Guillaume Smet" <guillaume(dot)smet(at)gmail(dot)com> |
---|---|
To: | "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | "Martijn van Oosterhout" <kleptog(at)svana(dot)org>, pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: [NOVICE] encoding problems |
Date: | 2008-05-07 09:30:16 |
Message-ID: | 1d4e0c10805070230m308bef9bu8b00b5f0a79f23cb@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers pgsql-novice pgsql-patches |
On Wed, Mar 12, 2008 at 4:35 PM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> 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.
Is there any plan to fix this behaviour in 8.3 branch? For instance,
the pg_stat_activity output is far less readable than before when
people use tabs to indent the SQL queries in their applications. From
my experience, it's pretty common and it's really a regression from
the usability point of view.
Regards,
--
Guillaume
From | Date | Subject | |
---|---|---|---|
Next Message | Simon Riggs | 2008-05-07 11:05:59 | Re: Concurrent psql API |
Previous Message | Richard Huxton | 2008-05-07 09:23:44 | Re: alter + preserving dependencies |
From | Date | Subject | |
---|---|---|---|
Next Message | Bruce Momjian | 2008-05-07 15:47:50 | Re: [NOVICE] encoding problems |
Previous Message | Wright, George | 2008-05-06 14:52:14 | Re: function exception |
From | Date | Subject | |
---|---|---|---|
Next Message | Simon Riggs | 2008-05-07 11:05:59 | Re: Concurrent psql API |
Previous Message | KaiGai Kohei | 2008-05-07 09:02:15 | Re: [0/4] Proposal of SE-PostgreSQL patches |