Hi Merlin, Below is the log captured when the crash was encountered.
STATEMENT: select count(1) from pg_ls_dir(current_setting('data_directory')) where pg_ls_dir = 'backup_label' LOG: 00000: duration: 4.083 ms LOCATION: exec_simple_query, postgres.c:1145 DEBUG: 00000: shmem_exit(0): 7 callbacks to make LOCATION: shmem_exit, ipc.c:212 DEBUG: 00000: proc_exit(0): 3 callbacks to make LOCATION: proc_exit_prepare, ipc.c:184 DEBUG: 00000: exit(0) LOCATION: proc_exit, ipc.c:135 DEBUG: 00000: shmem_exit(-1): 0 callbacks to make LOCATION: shmem_exit, ipc.c:212 DEBUG: 00000: proc_exit(-1): 0 callbacks to make LOCATION: proc_exit_prepare, ipc.c:184 DEBUG: 00000: reaping dead processes LOCATION: reaper, postmaster.c:2669 DEBUG: 00000: server process (PID 11104) exited with exit code 0 LOCATION: LogChildExit, postmaster.c:3385 DEBUG: 00000: reaping dead processes LOCATION: reaper, postmaster.c:2669 LOG: 00000: startup process (PID 10265) was terminated by signal 6: Aborted LOCATION: LogChildExit, postmaster.c:3407 LOG: 00000: terminating any other active server processes LOCATION: HandleChildCrash, postmaster.c:3134 DEBUG: 00000: sending SIGQUIT to process 10994 LOCATION: HandleChildCrash, postmaster.c:3233 DEBUG: 00000: sending SIGQUIT to process 10269 LOCATION: HandleChildCrash, postmaster.c:3263 DEBUG: 00000: sending SIGQUIT to process 10268 LOCATION: HandleChildCrash, postmaster.c:3275 WARNING: 57P02: terminating connection because of crash of another server process DETAIL: The postmaster has commanded this server process to roll back the current transaction and exit, because another server process exited abnormally and possibly corrupted shared memory. HINT: In a moment you should be able to reconnect to the database and repeat your command. Backtrace of the core generated: (gdb) bt #0 0x0000005563bcf9c0 in raise () from /lib64/libc.so.6 #1 0x0000005563bd42bc in abort () from /lib64/libc.so.6 #2 0x000000012039e228 in errfinish () #3 0x000000012039ef08 in elog_finish () #4 0x000000012009eb08 in btree_redo () #5 0x00000001200caff8 in StartupXLOG () #6 0x0000000120259958 in StartupProcessMain () #7 0x00000001200d590c in AuxiliaryProcessMain () #8 0x0000000120253434 in ?? () Let me know if any further clarification/information is needed. Regards, Sandhya -----Original Message----- From: Merlin Moncure [mailto:mmonc...@gmail.com] Sent: Tuesday, April 25, 2017 8:01 PM To: K S, Sandhya (Nokia - IN/Bangalore) <sandhya....@nokia.com> Cc: email@example.com; t...@sss.pgh.pa.us; pgsql-b...@postgresql.org; Itnal, Prakash (Nokia - IN/Bangalore) <prakash.it...@nokia.com>; T, Rasna (Nokia - IN/Bangalore) <rasn...@nokia.com> Subject: Re: [BUGS] Crash observed during the start of the Postgres process On Tue, Apr 25, 2017 at 8:44 AM, K S, Sandhya (Nokia - IN/Bangalore) <sandhya....@nokia.com> wrote: > Hello, > > Did you get a chance to take a look into the issue? > > Please consider it with high priority. We will be awaiting your inputs. This email is heavily cross posted, which is obnoxious. Can you paste the relevant log snippet? merlin -- Sent via pgsql-hackers mailing list (firstname.lastname@example.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers