RE: logical decoding and replication of sequences, take 2 - Mailing list pgsql-hackers

From Zhijie Hou (Fujitsu)
Subject RE: logical decoding and replication of sequences, take 2
Date
Msg-id OS0PR01MB5716063A630380EFC1C9F7A694FCA@OS0PR01MB5716.jpnprd01.prod.outlook.com
Whole thread Raw
In response to RE: logical decoding and replication of sequences, take 2  ("Zhijie Hou (Fujitsu)" <houzj.fnst@fujitsu.com>)
List pgsql-hackers
On Friday, September 15, 2023 11:11 AM Zhijie Hou (Fujitsu) <houzj.fnst@fujitsu.com> wrote:
> 
> On Wednesday, August 16, 2023 10:27 PM Tomas Vondra
> <tomas.vondra@enterprisedb.com> wrote:
> 
> Hi,
> 
> >
> >
> > I guess we could update the origin, per attached 0004. We don't have
> > timestamp to set replorigin_session_origin_timestamp, but it seems we
> > don't need that.
> >
> > The attached patch merges the earlier improvements, except for the
> > part that experimented with adding a "fake" transaction (which turned
> > out to have a number of difficult issues).
> 
> I tried to test the patch and found a crash when calling
> pg_logical_slot_get_changes() to consume sequence changes.

Oh, after confirming again, I realize it's my fault that my build environment
was not clean. This case passed after rebuilding. Sorry for the noise.

Best Regards,
Hou zj

pgsql-hackers by date:

Previous
From: Yugo NAGATA
Date:
Subject: Doc: vcregress .bat commands list lacks "taptest"
Next
From: Daniel Gustafsson
Date:
Subject: Re: Clarify where the severity level is defined