From: | "Bossart, Nathan" <bossartn(at)amazon(dot)com> |
---|---|
To: | Magnus Hagander <magnus(at)hagander(dot)net>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | Vik Fearing <vik(at)postgresfriends(dot)org>, Peter Eisentraut <peter(dot)eisentraut(at)enterprisedb(dot)com>, Andres Freund <andres(at)anarazel(dot)de>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
Subject: | Re: Catalog version access |
Date: | 2021-08-16 18:12:54 |
Message-ID: | 58A2BF44-855D-466F-91CC-8355AF581707@amazon.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On 4/8/21, 2:58 AM, "Magnus Hagander" <magnus(at)hagander(dot)net> wrote:
> Another option could be to provide a switch to the postmaster binary.
> Using pg_config as originally suggested is risky because you might
> pick up the wrong postmaster, but if you put it on the actual
> postmaster binary you certainly know which one you're on... As this is
> something that's primarily of interest to developers, it's also a bit
> lower weight than having a "heavy" solution like an entire mode for
> pg_ctl.
I was looking at the --check switch for the postgres binary recently
[0], and this sounds like something that might fit in nicely there.
In the attached patch, --check will also check the control file if one
exists.
Nathan
[0] https://postgr.es/m/0545F7B3-70C0-4DE8-8C85-EAFE6113B7EE%40amazon.com
Attachment | Content-Type | Size |
---|---|---|
v1-0001-Check-control-file-in-check-mode.patch | application/octet-stream | 1.3 KB |
From | Date | Subject | |
---|---|---|---|
Next Message | Daniel Gustafsson | 2021-08-16 18:13:02 | Re: Emit namespace in post-copy output |
Previous Message | Peter Geoghegan | 2021-08-16 17:35:45 | The Free Space Map: Problems and Opportunities |