pg.ddx.io  pgsql-hackers@postgresql.org mailing list archive  

help / color / mirror / Atom feed
From: Peter Eisentraut <peter.eisentraut@enterprisedb.com>
To: Amit Kapila <amit.kapila16@gmail.com>
To: Masahiko Sawada <sawada.mshk@gmail.com>
Cc: PostgreSQL-development <pgsql-hackers@postgresql.org>
Subject: Re: Skipping logical replication transactions on subscriber side
Date: Mon, 31 May 2021 21:25:55 +0200
Message-ID: <bd954841-596d-c212-9a13-6f9747cc8903@enterprisedb.com> (raw)
In-Reply-To: <CAA4eK1K=9Z1qTRQ8FDUuoK1r4te9TgUHka97cG0Ua65SaTyEPg@mail.gmail.com>
References: <CAD21AoDeScrsHhLyEPYqN3sydg6PxAPVBboK=30xJfUVihNZDA@mail.gmail.com>
	<CAA4eK1+MkrsHRTdFJiYF82UE3rXBU2QcQfzH-3i_u4RFzapCsw@mail.gmail.com>
	<CAD21AoCxC5rAR9hdAu5HLWbkNx5jR6boSeDfj=8ph5-fWtjxuQ@mail.gmail.com>
	<CAA4eK1+Ghs131feWdYZd1VJ9ozeRXEoH3gcF1OtNe3RW557wew@mail.gmail.com>
	<CAD21AoCmMahD+EQB+HK7n8oM_hjMqytNm73rDhLdFPPtoYG+-w@mail.gmail.com>
	<CAA4eK1LTE-AYtwatvLzAw+Vy53C92QHoB7-rVbX-9nf8ws2Vag@mail.gmail.com>
	<CAD21AoDyGQNVDUyY2b3=hfPm359GUP=Yep7i=ojL42cP+QAmpQ@mail.gmail.com>
	<CAA4eK1K=9Z1qTRQ8FDUuoK1r4te9TgUHka97cG0Ua65SaTyEPg@mail.gmail.com>

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.





view thread (590+ messages)  latest in thread

Message-ID: <bd954841-596d-c212-9a13-6f9747cc8903@enterprisedb.com>
Permalink:  ../bd954841-596d-c212-9a13-6f9747cc8903@enterprisedb.com/
Also on:    postgresql.org/message-id/bd954841-596d-c212-9a13-6f9747cc8903@enterprisedb.com

 · 

reply
Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: pgsql-hackers@postgresql.org
  Cc: peter.eisentraut@enterprisedb.com, amit.kapila16@gmail.com, sawada.mshk@gmail.com
  Subject: Re: Skipping logical replication transactions on subscriber side
  In-Reply-To: <bd954841-596d-c212-9a13-6f9747cc8903@enterprisedb.com>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox