| From: | "osumi(dot)takamichi(at)fujitsu(dot)com" <osumi(dot)takamichi(at)fujitsu(dot)com> |
|---|---|
| To: | "osumi(dot)takamichi(at)fujitsu(dot)com" <osumi(dot)takamichi(at)fujitsu(dot)com>, 'Masahiko Sawada' <sawada(dot)mshk(at)gmail(dot)com> |
| Cc: | "'pgsql-hackers(at)lists(dot)postgresql(dot)org'" <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Subject: | RE: Enhance traceability of wal_level changes for backup management |
| Date: | 2021-01-28 00:44:06 |
| Message-ID: | OSBPR01MB4888FC18E1C514226C06E066EDBA9@OSBPR01MB4888.jpnprd01.prod.outlook.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | 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 | Content-Type | Size |
|---|---|---|
| trace_wal_level_drop_v01.patch | application/octet-stream | 9.5 KB |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Julien Rouhaud | 2021-01-28 00:49:54 | Re: protect pg_stat_statements_info() for being used without the library loaded |
| Previous Message | Zhihong Yu | 2021-01-28 00:32:38 | Re: [HACKERS] GSoC 2017: Foreign Key Arrays |