| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Stefan Kaltenbrunner <stefan(at)kaltenbrunner(dot)cc> |
| Cc: | Postgresql Hackers Mailinglist <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: (full) Memory context dump considered harmful |
| Date: | 2015-08-20 16:09:44 |
| Message-ID: | 21096.1440086984@sss.pgh.pa.us |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Stefan Kaltenbrunner <stefan(at)kaltenbrunner(dot)cc> writes:
> I wonder if we should have a default of capping the dump to say 1k lines
> or such and only optionally do a full one.
-1. It's worked like this for the last fifteen years or thereabouts,
and you're the first one to complain. I suspect some weirdness in
your logging setup, rather than any systemic problem that we
need to lobotomize our diagnostic output in order to prevent.
(The reason I say "lobotomize" is that there's no particularly good
reason to assume that the first N lines will tell you what you need
to know. And the filter rule would have to be *very* stupid, because
we can't risk trying to allocate any additional memory to track what
we're doing here.)
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Shulgin, Oleksandr | 2015-08-20 16:27:11 | Re: deparsing utility commands |
| Previous Message | Corey Huinker | 2015-08-20 16:00:19 | Re: Declarative partitioning |