| From: | Michael Paquier <michael(at)paquier(dot)xyz> |
|---|---|
| To: | Fujii Masao <masao(dot)fujii(at)oss(dot)nttdata(dot)com> |
| Cc: | Nathan Bossart <nathandbossart(at)gmail(dot)com>, 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 04:19:52 |
| Message-ID: | ZwSy6GdoqG2KUm1O@paquier.xyz |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Tue, Oct 08, 2024 at 12:41:16PM +0900, Fujii Masao wrote:
> 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.
My argument is about knowing the size of each file, for monitoring of
disk space. The retention can be controlled by a GUC based on time,
and this function requires knowing about the file name format.
--
Michael
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andrei Lepikhov | 2024-10-08 04:24:01 | Re: Consider the number of columns in the sort cost model |
| Previous Message | Andrei Lepikhov | 2024-10-08 03:54:02 | Re: Removing unneeded self joins |