Skip site navigation (1) Skip section navigation (2)

Re: pg_dump --pretty-print-views

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-30 16:03:27
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-hackers
Andrew Dunstan <andrew(at)dunslane(dot)net> writes:
> On 01/30/2013 09:58 AM, Tom Lane wrote:
>> Marko Tiikkaja <pgmail(at)joh(dot)to> writes:
>>> On 1/30/13 7:52 AM, Jeevan Chalke wrote:
>>>> However, I am not sure about putting "WRAP_COLUMN_DEFAULT" by default. In
>>>> my opinion we should put that by default but other people may object so I
>>>> will keep that in code committors plate.

>> FWIW, I'd vote for not enabling that by default --- it's basically an
>> unwarranted assumption about how wide people's terminal windows are.

> I'm not exactly sure what you're arguing for.

Maybe I'm confused - I thought the alternative Jeevan was talking about
was that we enable PRETTY_INDENT processing by default, but not
wrapColumn processing.

			regards, tom lane

In response to


pgsql-hackers by date

Next:From: Zoltán BöszörményiDate: 2013-01-30 16:45:54
Subject: Re: Strange Windows problem, lock_timeout test request
Previous:From: Jeff JanesDate: 2013-01-30 15:58:07
Subject: Re: autovacuum not prioritising for-wraparound tables

Privacy Policy | About PostgreSQL
Copyright © 1996-2018 The PostgreSQL Global Development Group