| From: | Michael Paquier <michael(at)paquier(dot)xyz> |
|---|---|
| To: | Bharath Rupireddy <bharath(dot)rupireddyforpostgres(at)gmail(dot)com> |
| Cc: | Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org>, "Bossart, Nathan" <bossartn(at)amazon(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: add recovery, backup, archive, streaming etc. activity messages to server logs along with ps display |
| Date: | 2021-12-08 07:21:55 |
| Message-ID: | YbBdE0nfVcSkffPg@paquier.xyz |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Wed, Dec 08, 2021 at 10:47:57AM +0530, Bharath Rupireddy wrote:
> Thanks for taking a look at the patch. How about the attached v4?
>
> I added a CF entry - https://commitfest.postgresql.org/36/3443/
+ else if (source == XLOG_FROM_STREAM)
+ ereport(LOG,
+ (errmsg("recovering WAL segment \"%s\" received from primary",
+ xlogfname)));
This is incorrect when using a cascading standby. And perhaps this
could use a switch/case?
While quickly testing, I got reminded that the LOG for a segment
retrieved from the local pg_wal would generate some noise when running
for example the bootstrap process. Is this one really interesting
compared to the two others?
--
Michael
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Michael Paquier | 2021-12-08 07:31:42 | Re: Make pg_waldump report replication origin ID, LSN, and timestamp. |
| Previous Message | Masahiko Sawada | 2021-12-08 07:05:49 | Re: Skipping logical replication transactions on subscriber side |