Re: Current master hangs under the debugger after Parallel Seq Scan (Linux, MacOS) - Mailing list pgsql-hackers

From Robert Haas
Subject Re: Current master hangs under the debugger after Parallel Seq Scan (Linux, MacOS)
Date
Msg-id CA+TgmoaUrK8U+Osa72+qAUhZUq7PD8pbF8+6JrZgoxVQ2ozWVg@mail.gmail.com
Whole thread Raw
In response to Re: Current master hangs under the debugger after Parallel Seq Scan (Linux, MacOS)  (Nikita Malakhov <hukutoc@gmail.com>)
List 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



pgsql-hackers by date:

Previous
From: Nikolay Shaplov
Date:
Subject: Re: vacuum_truncate configuration parameter and isset_offset
Next
From: "David G. Johnston"
Date:
Subject: Re: vacuum_truncate configuration parameter and isset_offset