| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | John R Pierce <pierce(at)hogranch(dot)com> |
| Cc: | pgsql-bugs(at)postgresql(dot)org |
| Subject: | Re: Confusing error message with too-large file in pg_basebackup |
| Date: | 2015-11-20 22:34:34 |
| Message-ID: | 31556.1448058874@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
John R Pierce <pierce(at)hogranch(dot)com> writes:
> On 11/20/2015 2:13 PM, Tom Lane wrote:
>> It'd be reasonable to skip 'em if we can identify 'em reliably. I'm
>> not sure how reliably we can do that though.
> aren't they nearly always named 'core' ?
No. Modern systems more often call them something like 'core.<pid>'.
What really makes it messy is that the name is user-configurable on
most Linux kernels, see /proc/sys/kernel/core_pattern.
We could probably get away with excluding anything that matches "*core*",
but it wouldn't be bulletproof.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2015-11-21 00:11:23 | Re: Confusing error message with too-large file in pg_basebackup |
| Previous Message | John R Pierce | 2015-11-20 22:25:59 | Re: Confusing error message with too-large file in pg_basebackup |