From: | Masahiko Sawada <sawada(dot)mshk(at)gmail(dot)com> |
---|---|
To: | Alexander Lakhin <exclusion(at)gmail(dot)com> |
Cc: | pgsql-bugs(at)lists(dot)postgresql(dot)org, Andres Freund <andres(at)anarazel(dot)de> |
Subject: | Re: BUG #18031: Segmentation fault after deadlock within VACUUM's parallel worker |
Date: | 2023-07-24 01:39:54 |
Message-ID: | CAD21AoCkpvU97e0Wrgo=Rzz=tQ43dR8M8NWGTnY=RV94Qa81-A@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs |
On Sat, Jul 22, 2023 at 7:00 PM Alexander Lakhin <exclusion(at)gmail(dot)com> wrote:
>
> Hello Sawada-san,
>
> 21.07.2023 11:01, Masahiko Sawada wrote:
> > ...
> > leading to calling RemoveFromWaitQueue() again. I think we should use
> > dclist_delete_from_thoroughly() instead. With the attached patch, the
> > issue doesn't happen in my environment.
>
> Thank you for the analysis and the patch! It fixes the issue for me too.
Thank you for the confirmation. I found this issue is the same as one
that has already been reported[1].
>
> > Another thing I noticed is that the Assert(waitLock) in
> > RemoveFromWaitQueue() is useless actually, since we access *waitLock
> > before that:
>
> Yeah, I also noticed that, and a simple grep-based script with a little
> eyeballing discovered one similar Assert usage:
>
> void
> llvm_split_symbol_name(const char *name, char **modname, char **funcname)
> {
> ...
> *funcname = rindex(name, '.');
> (*funcname)++; /* jump over . */
>
> *modname = pnstrdup(name + strlen("pgextern."),
> *funcname - name - strlen("pgextern.") - 1);
> Assert(funcname);
>
> May be it's worth to fix it in passing.
Yeah, but it should be discussed on another thread.
[1] https://www.postgresql.org/message-id/ZKy4AdrLEfbqrxGJ%40telsasoft.com
--
Masahiko Sawada
Amazon Web Services: https://aws.amazon.com
From | Date | Subject | |
---|---|---|---|
Next Message | Zechman, Derek S | 2023-07-24 15:05:15 | pg_hba.conf "authentication file token too long, skipping" |
Previous Message | Alexander Lakhin | 2023-07-22 10:00:00 | Re: BUG #18031: Segmentation fault after deadlock within VACUUM's parallel worker |