Re: BUG #16145: Not able to terminate active session

From: Tomas Vondra <tomas(dot)vondra(at)2ndquadrant(dot)com>
To: MOHAN KUMAR DORAIRAJ <mohankumar(dot)dorairaj(at)globalfoundries(dot)com>
Cc: pgsql-bugs(at)lists(dot)postgresql(dot)org
Subject: Re: BUG #16145: Not able to terminate active session
Date: 2019-12-03 16:38:18
Message-ID: 20191203163818.vi4ocgg7mfo53fbz@development
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

On Wed, Dec 04, 2019 at 12:26:14AM +0800, MOHAN KUMAR DORAIRAJ wrote:
>Dear Tomas
>
>Please find the info
>
>
>-bash-4.2$ gdb -p 16647
>GNU gdb (GDB) Red Hat Enterprise Linux 7.6.1-115.el7
>Copyright (C) 2013 Free Software Foundation, Inc.
>License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html
>>
>This is free software: you are free to change and redistribute it.
>There is NO WARRANTY, to the extent permitted by law. Type "show copying"
>and "show warranty" for details.
>This GDB was configured as "x86_64-redhat-linux-gnu".
>For bug reporting instructions, please see:
><http://www.gnu.org/software/gdb/bugs/>.
>Attaching to process 16647
>Reading symbols from /usr/pgsql-11/bin/postgres...Reading symbols from
>/usr/pgsql-11/bin/postgres...(no debugging symbols found)...done.
>(no debugging symbols found)...done.
>Reading symbols from /lib64/libpthread.so.0...(no debugging symbols
>found)...done.
>[Thread debugging using libthread_db enabled]
>Using host libthread_db library "/lib64/libthread_db.so.1".
>...
>Reading symbols from /db/oraclnt/12.2.0/lib/libnque12.so...(no debugging
>symbols found)...done.
>Loaded symbols for /db/oraclnt/12.2.0/lib/libnque12.so
>0x00007f5503e826e0 in __read_nocancel () from /lib64/libpthread.so.0
>Missing separate debuginfos, use: debuginfo-install
>postgresql11-server-11.2-2PGDG.rhel7.x86_64
>(gdb) quit
>A debugging session is active.
>
> Inferior 1 [process 16647] will be detached.
>
>Quit anyway? (y or n) y
>Detaching from program: /usr/pgsql-11/bin/postgres, process 16647
>

This is still just the initial info gdb shows after attaching to the
process. You need to do "bt" or "backtrace" before quitting.

regards

--
Tomas Vondra http://www.2ndQuadrant.com
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Tom Lane 2019-12-03 16:57:57 Re: pg_dump losing index column collations for unique and primary keys
Previous Message Alexey Bashtanov 2019-12-03 16:35:20 pg_dump losing index column collations for unique and primary keys