Re: Move global variables of pgoutput to plugin private scope. - Mailing list pgsql-hackers

From Michael Paquier
Subject Re: Move global variables of pgoutput to plugin private scope.
Date
Msg-id ZRPgUl--ET838JAq@paquier.xyz
Whole thread Raw
In response to Re: Move global variables of pgoutput to plugin private scope.  (Amit Kapila <amit.kapila16@gmail.com>)
Responses Re: Move global variables of pgoutput to plugin private scope.
List pgsql-hackers
On Wed, Sep 27, 2023 at 10:51:52AM +0530, Amit Kapila wrote:
> I have briefly looked at
> v2-0002-Move-in_streaming-to-output-private-data in the same email [1]
> but didn't think about it in detail (like whether there is any live
> bug that can be fixed or is just an improvement).

This looks like an improvement to me, as at the startup of a stream
the flag is forcibly reset to a false state.  So, you cannot really
reach a state where a second stream could be started within the same
session but with a flag incorrectly set to true.  Tracking that in the
state data of pgoutput is cleaner, definitely.

> If you wanted to
> look and commit v2-0002-Move-in_streaming-to-output-private-data, I am
> fine with that?

Sure.  I found the concept behind 0002 sound.  Feel free to go ahead
with 0001, and I can always look at the second.  Always happy to help.
--
Michael

Attachment

pgsql-hackers by date:

Previous
From: David Rowley
Date:
Subject: Re: Avoid a possible out-of-bounds access (src/backend/optimizer/util/relnode.c)
Next
From: David Rowley
Date:
Subject: Re: make add_paths_to_append_rel aware of startup cost