Re: Move global variables of pgoutput to plugin private scope.
Michael Paquier <michael@paquier.xyz>
From: Michael Paquier <michael@paquier.xyz>
To: Amit Kapila <amit.kapila16@gmail.com>
Cc: "Zhijie Hou (Fujitsu)" <houzj.fnst@fujitsu.com>, PostgreSQL Hackers <pgsql-hackers@lists.postgresql.org>
Date: 2023-09-29T01:41:04Z
Lists: pgsql-hackers
On Wed, Sep 27, 2023 at 04:57:06PM +0900, Michael Paquier wrote: > 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. For the sake of the archives: - Amit has applied 0001 down to 16 as of 54ccfd65868c. - I've applied 0002 after on HEAD as of 9210afd3bcd6. -- Michael
Commits
-
Move tracking of in_streaming to PGOutputData
- 9210afd3bcd6 17.0 landed
-
Fix the misuse of origin filter across multiple pg_logical_slot_get_changes() calls.
- 54ccfd65868c 17.0 landed
- 8d05be93197c 16.1 landed
-
Fix typos in pgoutput.c
- c868cbfef70a 17.0 landed