| From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
|---|---|
| To: | Andy Fan <zhihui(dot)fan1213(at)gmail(dot)com> |
| Cc: | PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: No core file generated after PostgresNode->start |
| Date: | 2020-05-11 19:35:51 |
| Message-ID: | CA+TgmobfEAhvmeNpq0RxYpQHcWyKfyAYMhTcA9QObQA3GVp1WA@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Sun, May 10, 2020 at 11:21 PM Andy Fan <zhihui(dot)fan1213(at)gmail(dot)com> wrote:
> Looks this doesn't mean a crash. If the test case(subscription/t/013_partition.pl)
> failed, test framework kill some process, which leads the above message. So you can
> ignore this issue now. Thanks
I think there might be a real issue here someplace, though, because I
couldn't get a core dump last week when I did have a crash happening
locally. I didn't poke into it very hard though so I never figured out
exactly why not, but ulimit -c unlimited didn't help.
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Robert Haas | 2020-05-11 19:43:17 | Re: COPY, lock release and MVCC |
| Previous Message | Robert Haas | 2020-05-11 19:20:23 | Re: gcov coverage data not full with immediate stop |