Hi Craig,
The scenario is lock and unlock of the system for 30 times. During this scenario 5 sh-QUIT core is generated. GDB of 5 core is pointing to different locations.
I have attached output for 2 such instance.
Regards,
Sandhya
From: Craig Ringer [mailto:craig@2ndquadrant.com]
Sent: Friday, July 07, 2017 12:55 PM
To: K S, Sandhya (Nokia - IN/Bangalore) <sandhya.k_s@nokia.com>
Cc: pgsql-bugs <pgsql-bugs@postgresql.org>; PostgreSQL Hackers <pgsql-hackers@postgresql.org>; T, Rasna (Nokia - IN/Bangalore) <rasna.t@nokia.com>; Itnal, Prakash (Nokia - IN/Bangalore) <prakash.itnal@nokia.com>
Subject: Re: [HACKERS] Postgres process invoking exit resulting in sh-QUIT core
On 7 July 2017 at 15:10, K S, Sandhya (Nokia - IN/Bangalore) <sandhya.k_s@nokia.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' ?
--