Re: BUG #18014: Releasing catcache entries makes schema_to_xmlschema() fail when parallel workers are used

From: Kyotaro Horiguchi <horikyota(dot)ntt(at)gmail(dot)com>
To: tgl(at)sss(dot)pgh(dot)pa(dot)us
Cc: exclusion(at)gmail(dot)com, pgsql-bugs(at)lists(dot)postgresql(dot)org
Subject: Re: BUG #18014: Releasing catcache entries makes schema_to_xmlschema() fail when parallel workers are used
Date: 2023-07-26 08:36:00
Message-ID: 20230726.173600.1959099538779757634.horikyota.ntt@gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

At Wed, 26 Jul 2023 11:59:56 +0900 (JST), Kyotaro Horiguchi <horikyota(dot)ntt(at)gmail(dot)com> wrote in
> Yeah, as I posted at the same time, what I meant is not that the
> sequence is unsafe. It is safe even on a parallel worker. What I
> meant was that there seems to be a case where it returns different
> result for the same parameters if they are called on different
> workers.

Okey, I'm convinced that that won't happen, due to command counter,
which was missing in the above.

Sorry for the noise.

regards.

--
Kyotaro Horiguchi
NTT Open Source Software Center

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message Magnus Hagander 2023-07-26 11:08:51 Re: BUG #18036: Query planner chooses sub-optimal query path given enough IN tuples.
Previous Message Masahiko Sawada 2023-07-26 05:55:23 Re: BUG #18031: Segmentation fault after deadlock within VACUUM's parallel worker