Horton

Re: Current master hangs under the debugger after Parallel Seq Scan (Linux, MacOS)

Robert Haas <robertmhaas@gmail.com>

View thread
From: Robert Haas <robertmhaas@gmail.com>
To: Nikita Malakhov <hukutoc@gmail.com>
Cc: Vladlen Popolitov <v.popolitov@postgrespro.ru>, Tom Lane <tgl@sss.pgh.pa.us>, pgsql-hackers@lists.postgresql.org, hukutoc@gmail.ru
Date: 2025-03-26T17:40:19Z
Lists: pgsql-hackers 
On Wed, Mar 26, 2025 at 12:32 PM Nikita Malakhov <hukutoc@gmail.com> wrote:
> Vladlen, I've checked your example and also got this behavior
> on the current master under Gdb (Ubuntu 22.04 LTS).
>
> On the query above server waits in this state (as shown by gdb):
> Program received signal SIGUSR1, User defined signal 1.
> 0x0000562beb21c6ed in ExecInterpExpr (state=0x562bec781858, econtext=<optimized out>, isnull=<optimized out>) at execExprInterp.c:625
> 625                             return state->resvalue;
>
> Although, the process continues to work normally after gdb is detached from it.

Do either of you have any theory as to how removing a cast could cause
this behavior?

The only idea that occurs to me is a bug in gdb.

-- 
Robert Haas
EDB: http://www.enterprisedb.com