Re: Enhance traceability of wal_level changes for backup management

From: Peter Eisentraut <peter(dot)eisentraut(at)enterprisedb(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-03-06 18:48:25
Message-ID: eb00b1b3-3a74-0aea-a1a7-f4f014ee4f82@enterprisedb.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 28.01.21 01:44, osumi(dot)takamichi(at)fujitsu(dot)com wrote:
>> (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.

It's not clear to me what this is supposed to accomplish. I read the
thread, but it's still not clear. What is one supposed to do with this
information?

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Joel Jacobson 2021-03-06 19:03:17 [PATCH] pg_permissions
Previous Message David Fetter 2021-03-06 18:37:59 Re: Feedback on table expansion hook (including patch)