| From: | Andres Freund <andres(at)anarazel(dot)de> |
|---|---|
| To: | Robert Haas <robertmhaas(at)gmail(dot)com> |
| 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:19:35 |
| Message-ID: | 20171212191935.y3gb2dk4tzgmzx65@alap3.anarazel.de |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 2017-12-12 14:16:59 -0500, Robert Haas wrote:
> 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.
That doesn't really work on some busy servers, and also often in cases
where the log potentially contains sensitive (e.g. HIPPA) data.
I think a function returning the dump would be great, a function "just"
dumping to the server log still pretty good.
Greetings,
Andres Freund
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2017-12-12 19:30:58 | Re: Rethinking MemoryContext creation |
| Previous Message | Robert Haas | 2017-12-12 19:16:59 | Re: Using ProcSignal to get memory context stats from a running backend |