RE: Enhance traceability of wal_level changes for backup management - Mailing list pgsql-hackers

From osumi.takamichi@fujitsu.com
Subject RE: Enhance traceability of wal_level changes for backup management
Date
Msg-id OSBPR01MB4888FC18E1C514226C06E066EDBA9@OSBPR01MB4888.jpnprd01.prod.outlook.com
Whole thread Raw
In response to RE: Enhance traceability of wal_level changes for backup management  ("osumi.takamichi@fujitsu.com" <osumi.takamichi@fujitsu.com>)
Responses Re: Enhance traceability of wal_level changes for backup management  (vignesh C <vignesh21@gmail.com>)
List pgsql-hackers
Hello


On Thursday, January 21, 2021 11:19 PM I wrote:
> If no one disagree with it, I'll proceed with (1) below.
>
> (1) writing the time or LSN in the control file to indicate when/where wal_level
> is changed to 'minimal'
> from upper level to invalidate the old backups or make alerts to users.
I attached the first patch which implementes this idea.
It was aligned by pgindent and shows no regression.

Best Regards,
    Takamichi Osumi


Attachment

pgsql-hackers by date:

Previous
From: Zhihong Yu
Date:
Subject: Re: [HACKERS] GSoC 2017: Foreign Key Arrays
Next
From: Julien Rouhaud
Date:
Subject: Re: protect pg_stat_statements_info() for being used without the library loaded