Re: Move global variables of pgoutput to plugin private scope.

From: Michael Paquier <michael(at)paquier(dot)xyz>
To: "Zhijie Hou (Fujitsu)" <houzj(dot)fnst(at)fujitsu(dot)com>
Cc: Amit Kapila <amit(dot)kapila16(at)gmail(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: Move global variables of pgoutput to plugin private scope.
Date: 2023-09-27 05:47:22
Message-ID: ZRPB6iEBdMSBb_g8@paquier.xyz
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

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

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message vignesh C 2023-09-27 05:47:42 Re: Invalidate the subscription worker in cases where a user loses their superuser status
Previous Message Michael Paquier 2023-09-27 05:46:01 Re: Could not run generate_unaccent_rules.py script when update unicode