| From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
|---|---|
| To: | Alvaro Herrera <alvherre(at)commandprompt(dot)com> |
| Cc: | "David E(dot) Wheeler" <david(at)kineticode(dot)com>, Peter Eisentraut <peter_e(at)gmx(dot)net>, Roger Leigh <rleigh(at)codelibre(dot)net>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: trailing whitespace in psql table output |
| Date: | 2010-09-27 17:53:45 |
| Message-ID: | AANLkTi=_CdE6vucKZ65x83S=aJVTgp=ZcGd5_TxY9210@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Mon, Sep 27, 2010 at 1:34 PM, Alvaro Herrera
<alvherre(at)commandprompt(dot)com> wrote:
> Excerpts from David E. Wheeler's message of lun sep 27 12:25:31 -0400 2010:
>> On Sep 27, 2010, at 5:05 AM, Peter Eisentraut wrote:
>>
>> > Um, no.
>> >
>> > In the meantime, I have arrived at the conclusion that doing this isn't
>> > worth it because it will break all regression test output. We can fix
>> > the stuff in our tree, but pg_regress is also used externally, and those
>> > guys would have a nightmare with this change. Perhaps if there is
>> > another more significant revision of the table style in the future, we
>> > should keep this issue in mind.
>>
>> Or change the way pg_regress works.
>
> Perhaps using unaligned mode? The problem with that is that it becomes
> very difficult to review changes to expected output.
Uh, yuck! If we don't care about changing the expected output, we can
just trim the whitespace as Peter suggested originally.
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise Postgres Company
| From | Date | Subject | |
|---|---|---|---|
| Next Message | David Fetter | 2010-09-27 18:09:04 | Re: trailing whitespace in psql table output |
| Previous Message | Nicolas Barbier | 2010-09-27 17:48:59 | Re: client socket TIME_WAIT state after PQfinish |