From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Andrew Dunstan <andrew(at)dunslane(dot)net> |
Cc: | Marko Tiikkaja <pgmail(at)joh(dot)to>, Jeevan Chalke <jeevan(dot)chalke(at)enterprisedb(dot)com>, David Fetter <david(at)fetter(dot)org>, PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: pg_dump --pretty-print-views |
Date: | 2013-01-31 01:31:27 |
Message-ID: | 18848.1359595887@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Andrew Dunstan <andrew(at)dunslane(dot)net> writes:
> On 01/30/2013 11:03 AM, Tom Lane wrote:
>>>> FWIW, I'd vote for not enabling that by default --- it's basically an
>>>> unwarranted assumption about how wide people's terminal windows are.
> Well, we could actually set the wrap value to 0, which would mean always
> wrap. That wouldn't be making any assumption about the user's terminal
> window size ;-)
I could live with that. I rather wonder actually if WRAP_COLUMN_DEFAULT
shouldn't be removed in favor of using 0 as the default. 80-column
windows may be our coding standard for Postgres, but that doesn't mean
they're not pretty passe elsewhere.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Amit Kapila | 2013-01-31 03:39:58 | Re: Review : Add hooks for pre- and post-processor executables for COPY and \copy |
Previous Message | Andrew Dunstan | 2013-01-31 01:07:42 | Re: pg_dump --pretty-print-views |