From: | Peter Smith <smithpb2250(at)gmail(dot)com> |
---|---|
To: | Bharath Rupireddy <bharath(dot)rupireddyforpostgres(at)gmail(dot)com> |
Cc: | Amit Kapila <amit(dot)kapila16(at)gmail(dot)com>, Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org>, Greg Stark <stark(at)mit(dot)edu>, Euler Taveira <euler(at)eulerto(dot)com>, Kyotaro Horiguchi <horikyota(dot)ntt(at)gmail(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
Subject: | Re: add log messages when replication slots become active and inactive (was Re: Is it worth adding ReplicationSlot active_pid to ReplicationSlotPersistentData?) |
Date: | 2023-11-07 01:33:07 |
Message-ID: | CAHut+PttGh6WzjB6ms_fzsXVkZwXnJA4wOaNYjwebJH0wXQuHw@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Hi,
FWIW, I used a small script to set up the following environment to
help observe the log messages written by this patch.
Node1 = primary; it creates a PUBLICATION
Node2 = physical standby; the publication is replicated here
Node3 = subscriber; it subscribes to the publication now on the standby Node2
~
In the log files you can see:
1. The "physical" message from the walsender of the primary (Node1)
e.g. 2023-11-06 18:59:58.094 AEDT [17091] LOG: walsender process with
PID 17091 acquired physical replication slot "pg_basebackup_17091"
2. The "logical" message from the pub/sub walsender of the standby (Node2)
e.g. 2023-11-06 19:16:29.053 AEDT [12774] LOG: walsender process with
PID 12774 acquired logical replication slot "sub1"
~
PSA the test script and logs
======
Kind Regards,
Peter Smith.
Fujitsu Australia
Attachment | Content-Type | Size |
---|---|---|
ps_setup.sh | text/x-sh | 2.4 KB |
sub.log | application/octet-stream | 30.1 KB |
primarydb.log | application/octet-stream | 67.7 KB |
standby.log | application/octet-stream | 70.1 KB |
From | Date | Subject | |
---|---|---|---|
Next Message | Amit Kapila | 2023-11-07 02:15:02 | Re: Making aggregate deserialization (and WAL receive) functions slightly faster |
Previous Message | John Morris | 2023-11-07 00:57:32 | Re: Atomic ops for unlogged LSN |