From: | Fujii Masao <masao(dot)fujii(at)oss(dot)nttdata(dot)com> |
---|---|
To: | Nathan Bossart <nathandbossart(at)gmail(dot)com>, Michael Paquier <michael(at)paquier(dot)xyz> |
Cc: | btogiwarayuushi <btogiwarayuushi(at)oss(dot)nttdata(dot)com>, pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: Function for listing pg_wal/summaries directory |
Date: | 2024-10-08 03:41:16 |
Message-ID: | 40217d8f-84e3-4cd1-9125-97c353bd937d@oss.nttdata.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | 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
From | Date | Subject | |
---|---|---|---|
Next Message | Andrei Lepikhov | 2024-10-08 03:54:02 | Re: Removing unneeded self joins |
Previous Message | Michael Paquier | 2024-10-08 03:39:26 | Re: Commit fest 2024-09 |