| 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-bugs <pgsql-bugs(at)postgresql(dot)org>, PostgreSQL Hackers <pgsql-hackers(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: Postgres process invoking exit resulting in sh-QUIT core |
| Date: | 2017-07-07 07:25:07 |
| Message-ID: | CAMsr+YE_Bvf4+WFkJQ+m3X4bmj-jwX6N4C8JqF4qxWBK9yzGfQ@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs pgsql-hackers |
On 7 July 2017 at 15:10, K S, Sandhya (Nokia - IN/Bangalore) <
sandhya(dot)k_s(at)nokia(dot)com> wrote:
> Hi Craig,
>
>
>
> You were right about the restore_command.
>
This all makes sense then.
PostgreSQL sends SIGQUIT for immediate shutdown to its children. So the
restore_command would get signalled too.
Can't immediately explain the exit code, and SIGQUIT should _not_ generate
a core file. Can you show the result of attaching 'gdb' to the core file
and running 'bt full' ?
--
Craig Ringer http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services
| From | Date | Subject | |
|---|---|---|---|
| Next Message | K S, Sandhya (Nokia - IN/Bangalore) | 2017-07-07 07:41:03 | Re: Postgres process invoking exit resulting in sh-QUIT core |
| Previous Message | K S, Sandhya (Nokia - IN/Bangalore) | 2017-07-07 07:10:08 | Re: Postgres process invoking exit resulting in sh-QUIT core |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Kuntal Ghosh | 2017-07-07 07:31:09 | Re: Error while copying a large file in pg_rewind |
| Previous Message | Michael Paquier | 2017-07-07 07:21:05 | Re: pg_stop_backup(wait_for_archive := true) on standby server |