Postgres Pro
Downloads
Home   >   mailing lists

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 ZRPB6iEBdMSBb_g8@paquier.xyz
Whole thread Raw
In response to RE: Move global variables of pgoutput to plugin private scope.  ("Zhijie Hou (Fujitsu)" <houzj.fnst@fujitsu.com>)
List pgsql-hackers
Tree view 
On Wed, Sep 27, 2023 at 04:51:29AM +0000, Zhijie Hou (Fujitsu) wrote:
> While searching the code, I noticed one postgres fork where the PGoutputData is
> used in other places, although it's a separate fork, but it seems better to
> discuss the removal separately.
>
> [1]
https://github.com/Tencent/TBase/blob/7cf7f8afbcab7290538ad5e65893561710be3dfa/src/backend/replication/walsender.c#L100

Indeed.  Interesting.
--
Michael
Attachment

pgsql-hackers by date:

Previous
From: Michael Paquier
Date:
Subject: Re: Could not run generate_unaccent_rules.py script when update unicode
Next
From: vignesh C
Date:
Subject: Re: Invalidate the subscription worker in cases where a user loses their superuser status