Re: Function for listing pg_wal/summaries directory - Mailing list pgsql-hackers

From Fujii Masao
Subject Re: Function for listing pg_wal/summaries directory
Date
Msg-id 40217d8f-84e3-4cd1-9125-97c353bd937d@oss.nttdata.com
Whole thread Raw
In response to Re: Function for listing pg_wal/summaries directory  (Nathan Bossart <nathandbossart@gmail.com>)
List pgsql-hackers

On 2024/10/07 23:35, Nathan Bossart wrote:
> On Mon, Oct 07, 2024 at 10:07:10AM +0900, Michael Paquier wrote:
>> On Fri, Oct 04, 2024 at 10:02:11AM -0500, Nathan Bossart wrote:
>>> Could you explain why you feel the existing support functions are
>>> insufficient?
>>
>> Because it is not possible to outsource the scan of pg_wal/summaries/
>> to a different role, no?
> 
> I was under the impression that you could do this with
> pg_available_wal_summaries() [0].
> 
> [0] https://www.postgresql.org/docs/current/functions-info.html#FUNCTIONS-INFO-WAL-SUMMARY

One benefit of supporting something like pg_ls_summariesdir() is that
it allows us to view the last modification time of each WAL summary file
and estimate when they'll be removed based on wal_summary_keep_time.

Of course, we could also extend the existing function to report
the last modification time if this use case is valid, though.

Regards,

-- 
Fujii Masao
Advanced Computing Technology Center
Research and Development Headquarters
NTT DATA CORPORATION




pgsql-hackers by date:

Previous
From: Erik Wienhold
Date:
Subject: Re: pgindent fails with perl 5.40
Next
From: jian he
Date:
Subject: Re: POC, WIP: OR-clause support for indexes