From: | Justin Pryzby <pryzby(at)telsasoft(dot)com> |
---|---|
To: | Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at> |
Cc: | "Bossart, Nathan" <bossartn(at)amazon(dot)com>, Christoph Moench-Tegeder <cmt(at)burggraben(dot)net>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: pg_ls_tmpdir(); AND, Function for listing archive_status directory |
Date: | 2018-10-01 15:37:37 |
Message-ID: | 20181001153737.GA8041@telsasoft.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Wed, Sep 26, 2018 at 10:36:03PM +0200, Laurenz Albe wrote:
> Bossart, Nathan wrote:
> > Attached is a patch to add a pg_ls_tmpdir() function that lists the
> > contents of a specified tablespace's pgsql_tmp directory. This is
> > very similar to the existing pg_ls_logdir() and pg_ls_waldir()
> > functions.
On Sun, Sep 30, 2018 at 10:59:20PM +0200, Christoph Moench-Tegeder wrote:
> while setting up monitoring for a new PostgreSQL instance, I noticed that
> there's no build-in way for a pg_monitor role to check the contents of
> the archive_status directory. We got pg_ls_waldir() in 10, but that
> only lists pg_wal - not it's (sic) subdirectory.
> It may make sense to have a generic function like
> pg_ls_dir(dirname text, tablespace oid)
> instead. But maybe that's taking it too far...
I see Cristoph has another pg_ls_* function, which suggests that Laurenz idea
is good, and a generic pg_ls function is desirable.
Justin
From | Date | Subject | |
---|---|---|---|
Next Message | Andres Freund | 2018-10-01 15:45:07 | Re: pg_ls_tmpdir() |
Previous Message | Bossart, Nathan | 2018-10-01 15:37:01 | Re: Add SKIP LOCKED to VACUUM and ANALYZE |