From: | Craig Ringer <craig(at)2ndquadrant(dot)com> |
---|---|
To: | "K S, Sandhya (Nokia - IN/Bangalore)" <sandhya(dot)k_s(at)nokia(dot)com> |
Cc: | "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org>, "pgsql-bugs(at)postgresql(dot)org" <pgsql-bugs(at)postgresql(dot)org>, "T, Rasna (Nokia - IN/Bangalore)" <rasna(dot)t(at)nokia(dot)com>, "Itnal, Prakash (Nokia - IN/Bangalore)" <prakash(dot)itnal(at)nokia(dot)com> |
Subject: | Re: [HACKERS] Postgres process invoking exit resulting in sh-QUIT core |
Date: | 2017-06-30 12:10:03 |
Message-ID: | CAMsr+YHOrsR_-4Z2gPBGDbg1fnF2MRjhHuqDN7bX_h95xPXbRQ@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs pgsql-hackers |
On 30 June 2017 at 17:41, K S, Sandhya (Nokia - IN/Bangalore)
<sandhya(dot)k_s(at)nokia(dot)com> wrote:
> When we checked the process listing during the time of core generation, we
> found Postgres startup process is invoking “sh -c exit 1”:
> 4518 9249 0.1 0.0 155964 2036 ? Ss 15:05 0:00 postgres:
> startup process waiting for 0000000100000000000002EB
Looks like an archive_command or restore_command .
If 'sh' is dumping core, you probably have issues at a low level in
the kernel, file system, etc. Check dmesg.
--
Craig Ringer http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services
From | Date | Subject | |
---|---|---|---|
Next Message | Manjula Bharathan | 2017-06-30 16:18:41 | *** glibc detected *** postgres: SELECT: double free or corruption (!prev): 0x0000000001e59de0 *** |
Previous Message | K S, Sandhya (Nokia - IN/Bangalore) | 2017-06-30 09:41:34 | Postgres process invoking exit resulting in sh-QUIT core |
From | Date | Subject | |
---|---|---|---|
Next Message | Peter Eisentraut | 2017-06-30 12:13:44 | Re: Code quality issues in ICU patch |
Previous Message | Masahiko Sawada | 2017-06-30 11:17:39 | Re: Fix doc of DROP SUBSCRIPTION |