Re: Skipping logical replication transactions on subscriber side - Mailing list pgsql-hackers

From Peter Eisentraut
Subject Re: Skipping logical replication transactions on subscriber side
Date
Msg-id bd954841-596d-c212-9a13-6f9747cc8903@enterprisedb.com
Whole thread Raw
In response to Re: Skipping logical replication transactions on subscriber side  (Amit Kapila <amit.kapila16@gmail.com>)
Responses Re: Skipping logical replication transactions on subscriber side
List pgsql-hackers
On 27.05.21 12:04, Amit Kapila wrote:
>>> Also, I am thinking that instead of a stat view, do we need
>>> to consider having a system table (pg_replication_conflicts or
>>> something like that) for this because what if stats information is
>>> lost (say either due to crash or due to udp packet loss), can we rely
>>> on stats view for this?
>> Yeah, it seems better to use a catalog.
>>
> Okay.

Could you store it shared memory?  You don't need it to be crash safe, 
since the subscription will just run into the same error again after 
restart.  You just don't want it to be lost, like with the statistics 
collector.



pgsql-hackers by date:

Previous
From: Peter Eisentraut
Date:
Subject: Re: CALL versus procedures with output-only arguments
Next
From: "Joel Jacobson"
Date:
Subject: Re: make world and install-world without docs