From: | Jeff Janes <jeff(dot)janes(at)gmail(dot)com> |
---|---|
To: | Andrew Dunstan <andrew(at)dunslane(dot)net> |
Cc: | Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com>, Robert Haas <robertmhaas(at)gmail(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: proposal - psql - show longest tables |
Date: | 2013-07-22 20:26:53 |
Message-ID: | CAMkU=1zGjqjxkgOYVOwaDFQXi_w4=1frTbP-RuW87_LTj09CBw@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Mon, Jul 22, 2013 at 12:40 PM, Andrew Dunstan <andrew(at)dunslane(dot)net> wrote:
>
> On 07/22/2013 03:11 PM, Pavel Stehule wrote:
>>
>> 2013/7/22 Robert Haas <robertmhaas(at)gmail(dot)com>:
>>
>>
>>> Rather than just continuing to add more imposible-to-remember syntax,
>>> we really need a better design here.
>>
>> do you have any tip?
>>
>>
>>
>
> I agree with Robert. My tip is this: when you're in a hole, the first thing
> to do is to stop digging.
I don't think that Pavel believes himself to be in a hole.
After setting up my .psqlrc file as I normally do, I could do this:
:rtsize limit 10;
But it doesn't have the 'MB' feature, and if I want to help someone
else I first have to explain to them how to set their .psqlrc file the
same as mine, which is rather a bummer.
Is looking for the biggest tables a common enough thing that it should
be available to everyone, without needing custom customization?
Cheers,
Jeff
From | Date | Subject | |
---|---|---|---|
Next Message | Greg Smith | 2013-07-22 20:27:40 | Re: [v9.4] row level security |
Previous Message | Robert Haas | 2013-07-22 20:23:14 | Re: [HACKERS] getting rid of SnapshotNow |