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:13:09 |
Message-ID: | 30859.1448057589@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:
> We still shouldn't be dumping core files as part of a pg_basebackup...
It'd be reasonable to skip 'em if we can identify 'em reliably. I'm
not sure how reliably we can do that though.
> but then, why was the core file even IN the $PGDATA directory, shouldn't
> it have been in some other dir, like the postgres daemon user's $HOME ?
No, that's standard behavior. (I know of no Unix-oid system that dumps
cores into your $HOME by default; it's normally either $PWD or some
reserved directory like /cores.)
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | John R Pierce | 2015-11-20 22:25:59 | Re: Confusing error message with too-large file in pg_basebackup |
Previous Message | John R Pierce | 2015-11-20 21:56:11 | Re: Confusing error message with too-large file in pg_basebackup |