| From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
|---|---|
| To: | Andres Freund <andres(at)anarazel(dot)de> |
| Cc: | Craig Ringer <craig(at)2ndquadrant(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Using ProcSignal to get memory context stats from a running backend |
| Date: | 2017-12-12 19:16:59 |
| Message-ID: | CA+TgmoaFbdszf7oDx_3AMWPqef3On-qE_u-HJe-nk=e319SPAQ@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Tue, Dec 12, 2017 at 2:12 PM, Andres Freund <andres(at)anarazel(dot)de> wrote:
> I agree that it's more reliable - I hope there's no meaningful safety
> difference. I think you overestimate users a bit however - far from
> most of them are going to be able to extract a very long log entry from
> a busy log file. There's no generally available easy way to copy a few
> pages of text from a logfile that's a few gigabytes large...
Well, a lot of users will send us the whole logfile rather than just
the relevant bits, but that doesn't bother me.
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andres Freund | 2017-12-12 19:19:35 | Re: Using ProcSignal to get memory context stats from a running backend |
| Previous Message | Andrew Dunstan | 2017-12-12 19:13:20 | Re: ALTER TABLE ADD COLUMN fast default |