| From: | Gilles Darold <gilles(dot)darold(at)dalibo(dot)com> |
|---|---|
| To: | Robert Haas <robertmhaas(at)gmail(dot)com> |
| Cc: | PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: [patch] Add schema total size to psql \dn+ |
| Date: | 2019-02-25 08:56:53 |
| Message-ID: | ba3432cd-511b-f419-d5ec-381bd3811dfc@dalibo.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Le 22/02/2019 à 17:06, Robert Haas a écrit :
> On Wed, Feb 20, 2019 at 5:26 PM Gilles Darold <gilles(dot)darold(at)dalibo(dot)com> wrote:
>> The attached simple patch adds this feature. Is there any cons adding
>> this information?
> Well, it'll take time to compute, maybe a lot of time if the database
> is big and the server is busy. Not sure how serious that problem can
> get.
>
I agree, this king of report should be reserved to a super user
voluntary action and not as a default psql behavior. Patch removed.
Best regards,
--
Gilles Darold
Consultant PostgreSQL
http://dalibo.com - http://dalibo.org
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Antonin Houska | 2019-02-25 09:00:31 | Re: Referential Integrity Checks with Statement-level Triggers |
| Previous Message | Gilles Darold | 2019-02-25 08:51:22 | Re: [patch] Add schema total size to psql \dn+ |