On Tue, Dec 15, 2020 at 11:00 AM Jammie <shailesh.jaml...@gmail.com> wrote: > > Thanks Amit for the response > > We are using pgJDBC sample program here > https://jdbc.postgresql.org/documentation/head/replication.html > > the setFlushLSN is coming from the pgJDBC only. > > git hub for APIs of pgJDBC methods available. > > https://github.com/pgjdbc/pgjdbc > > The second slot refers to "private" slot. > > So ""we are not doing reading from the stream' ==> It means that we are > having readPending call only from the shared slot then we get the > lastReceivedLSN() from stream and > send it back to stream as confirmed_flush_lsn for both private and shared > slot. We dont do readPending call to private slot. we will use private slot > only when we dont have choice. It is kind of reserver slot for us. >
I think this (not performing read/decode on the private slot) could be the reason why it lagging behind. If you want to use as a reserve slot then you probably want to at least perform pg_replication_slot_advance() to move it to the required position. The restart_lsn won't move unless you read/decode from that slot. -- With Regards, Amit Kapila.
