Re: \d+ for long view definitions?

From: Robert Haas <robertmhaas(at)gmail(dot)com>
To: David Fetter <david(at)fetter(dot)org>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Josh Berkus <josh(at)agliodbs(dot)com>, Peter Eisentraut <peter_e(at)gmx(dot)net>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: \d+ for long view definitions?
Date: 2009-09-01 19:11:45
Message-ID: 603c8f070909011211v6272ecffvd402a3a5b0d549c5@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Tue, Sep 1, 2009 at 3:01 PM, David Fetter<david(at)fetter(dot)org> wrote:
> On Tue, Sep 01, 2009 at 02:29:12PM -0400, Tom Lane wrote:
>> Robert Haas <robertmhaas(at)gmail(dot)com> writes:
>> > I think we should always or never show the view definition, not
>> > sometimes.
>>
>> Yeah.  I can live with \d not showing it and \d+ showing it --- as
>> Peter already mentioned, that would be consistent with \df behavior.
>> Making it depend on the length is just weird.
>
> As I see it, there are two independent issues here:
>
> * "Smart" display based on number of columns in the query and the psql window
> * Whether to display the view definition.
>
> I'm thinking on the second, \d should not display the definition, and
> \d+ should.
>
> On the first...could we go to \x-type display if the columns will
> overflow the terminal?

I don't understand exactly what you're proposing, but I don't think
flipping into \x mode based on the window size is ever a good idea.

...Robert

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Andrew Dunstan 2009-09-01 19:14:19 Re: 8.5 release notes idea
Previous Message David Fetter 2009-09-01 19:03:43 Re: Adding \ev view editor?