Re: Seeing new stuff in log after upgrading from 11 to 15 - Mailing list pgsql-general

From Dmitry O Litvintsev
Subject Re: Seeing new stuff in log after upgrading from 11 to 15
Date
Msg-id SA1PR09MB7311C351A55835B6C58903BDB9EC2@SA1PR09MB7311.namprd09.prod.outlook.com
Whole thread Raw
In response to Re: Seeing new stuff in log after upgrading from 11 to 15  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-general
Thanks for the quick reply! NP, I was just being extra cautious after upgrade.


________________________________________
From: Tom Lane <tgl@sss.pgh.pa.us>
Sent: Wednesday, May 15, 2024 6:50 PM
To: Dmitry O Litvintsev
Cc: pgsql-general@lists.postgresql.org
Subject: Re: Seeing new stuff in log after upgrading from 11 to 15

[EXTERNAL] – This message is from an external sender

Dmitry O Litvintsev <litvinse@fnal.gov> writes:
> After upgrade 11 -> 15 started to see these messages in hot standby log:

> < 2024-05-15 17:20:24.164 CDT  151879 > LOG:  restartpoint complete: wrote 296338 buffers (28.3%); 0 WAL file(s)
added,134 removed, 0 recycled; write=1619.469 s, sync=0.022 s, total=1619.539 s; sync files=1492, longest=0.002 s,
average=0.001s; distance=2195446 kB, estimate=4171347 kB 
> < 2024-05-15 17:20:24.164 CDT  151879 > LOG:  recovery restart point at 17AB8/47000140
> < 2024-05-15 17:20:24.164 CDT  151879 > DETAIL:  Last completed transaction was at log time 2024-05-15
17:20:24.138362-05.
> < 2024-05-15 17:20:24.167 CDT  151879 > LOG:  restartpoint starting: wal

> while running 11 the log was almost empty, and I did not modify verbosity settings...
> Queston : are above harmless and just informational?

This is checkpoint logging, which is on by default now (a decision
I didn't particularly approve of).  Feel free to set
"log_checkpoints = off" if you don't want it.

                        regards, tom lane



pgsql-general by date:

Previous
From: Tom Lane
Date:
Subject: Re: Seeing new stuff in log after upgrading from 11 to 15
Next
From: milist ujang
Date:
Subject: db was corrupted, ERROR: cannot freeze committed xmax; fix by deleting rows in catalog tables