public inbox for [email protected]
help / color / mirror / Atom feedFrom: Adrian Klaver <[email protected]>
To: Durgamahesh Manne <[email protected]>
Cc: pgsql-general <[email protected]>
Subject: Re: Records count mismatch with logical replication
Date: Thu, 23 Jan 2025 10:28:22 -0800
Message-ID: <[email protected]> (raw)
In-Reply-To: <CAJCZkoKvzBxjAZxfOsUpEmwmrtV33ZZaHC-d-yvF6RPAxoATkQ@mail.gmail.com>
References: <CAJCZko+gYNGiixGcqKAhjhLhUZ3QQg2rGs6nH7ZUNwTtjYLfGw@mail.gmail.com>
<[email protected]>
<CAJCZko+HhLFkiDLDPg3fscUEO4uWyEFT4_e6GBMeywnnwRC-rg@mail.gmail.com>
<[email protected]>
<CAJCZkoLZb5ON_T-YecS3-1sQjiGUVLdgKjS93thQyzZKiaWuFQ@mail.gmail.com>
<[email protected]>
<CAJCZkoJgAh_T_NJU5Jn3mzJJQE4LE-tDEjEyP37gKNR1X0cDWQ@mail.gmail.com>
<[email protected]>
<CAJCZkoLatfwsQ-puesPfjrYtUmaAwokWQvqShoTGfJ56QzLfQw@mail.gmail.com>
<[email protected]>
<CAJCZkoKvzBxjAZxfOsUpEmwmrtV33ZZaHC-d-yvF6RPAxoATkQ@mail.gmail.com>
On 1/23/25 09:54, Durgamahesh Manne wrote:
See comments in line below.
>
> Source Publication Side:
> archiving=> select * from pg_stat_replication;
There is missing information here.
Am I right in assuming this is for slot cls_eva_msa?
And that it going to same client_addr 10.80.0.168?
> client_hostname |
> client_port | 52506
> backend_start | 2025-01-23 16:58:04.697304+00
> backend_xmin |
> state | streaming
> sent_lsn | 16C7/BDE4BB48
> write_lsn | 16C7/BDE4BB48
> flush_lsn | 16C7/BDE4BB48
> replay_lsn | 16C7/BDE4BB48
> write_lag | 00:00:00.002271
> flush_lag | 00:00:00.002271
> replay_lag | 00:00:00.002271
> sync_priority | 0
> sync_state | async
> reply_time | 2025-01-23 17:34:39.901979+00
> -[ RECORD 2 ]----+------------------------------
> pid | 3501
> usesysid | 14604130
> usename | archiving
> application_name | cle_clm_mka
> client_addr | 10.80.0.168
> client_hostname |
> client_port | 55412
> backend_start | 2025-01-22 09:31:11.83963+00
> backend_xmin |
> state | streaming
> sent_lsn | 16C7/BDE4BB48
> write_lsn | 16C7/BDE4BB48
> flush_lsn | 16C7/BDE4BB48
> replay_lsn | 16C7/BDE4BB48
> write_lag | 00:00:00.001642
> flush_lag | 00:00:00.023143
> replay_lag | 00:00:00.001642
> sync_priority | 0
> sync_state | async
> reply_time | 2025-01-23 17:34:39.903052+00
The lag times are minimal.
Where the queries done below done at later time then those above?
> Subscription Side : archiving=> select * from pg_stat_subscription where
> subname = 'cls_eva_msa';
> -[ RECORD 1 ]---------+------------------------------
> subid | 1936652827
> subname | cls_eva_msa
> pid | 18746
> relid |
> received_lsn | 16C7/FB48DFE0
> last_msg_send_time | 2025-01-23 17:41:11.924562+00
> last_msg_receipt_time | 2025-01-23 17:41:11.933344+00
> latest_end_lsn | 16C7/FB48DFE0
> latest_end_time | 2025-01-23 17:41:11.924562+00
>
> archiving=> select * from pg_stat_subscription where subname =
> 'cle_clm_mka';
> -[ RECORD 1 ]---------+------------------------------
> subid | 1892055116
> subname | cle_clm_mka
> pid | 507
> relid |
> received_lsn | 16C7/FB8CDF68
> last_msg_send_time | 2025-01-23 17:41:17.375879+00
> last_msg_receipt_time | 2025-01-23 17:41:17.378932+00
> latest_end_lsn | 16C7/FB8CDF68
> latest_end_time | 2025-01-23 17:41:17.375879+00
>
> '... everything looks good' is an opinion not actual data.
> Correct
So what does the AWS dashboard show for the I/0 between the servers?
>
> Regards
> Durga Mahesh
--
Adrian Klaver
[email protected]
view thread (13+ messages) latest in thread
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: [email protected]
Cc: [email protected], [email protected], [email protected]
Subject: Re: Records count mismatch with logical replication
In-Reply-To: <[email protected]>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox