Sequence last value is different among primary and secondary - Mailing list pgsql-admin

From Kenny Bachman
Subject Sequence last value is different among primary and secondary
Date
Msg-id CAC0w7LJszznfQ7FmgPzFQBd=4t5y23cd0T1iU_D4g0+PG0X08w@mail.gmail.com
Whole thread Raw
Responses Re: Sequence last value is different among primary and secondary
List pgsql-admin
Hello Team,

I got a weird situation about the sequence value in PG 14.5 (rhel 8.6). The sequence's last value is different between primary and secondary nodes.

This sequence output belongs to the PRIMARY node:

SELECT * FROM "ACCOUNT_ITEM_SEQ" ;
 last_value | log_cnt | is_called
------------+---------+-----------
     105485 |      31 | t

This output belongs to the SECONDARY node:

SELECT * FROM "ACCOUNT_ITEM_SEQ" ;
 last_value | log_cnt | is_called
------------+---------+-----------
     105516 |       0 | t

There is no replication gap or lag between the nodes.
What is the reason behind this difference?

Thank you for your help and guidance in advance.
Will

pgsql-admin by date:

Previous
From: Rui DeSousa
Date:
Subject: Re: How to test replication without doing a failover
Next
From: Paul Smith
Date:
Subject: Re: Sequence last value is different among primary and secondary