| From: | "Euler Taveira" <euler(at)eulerto(dot)com> |
|---|---|
| To: | "Vik Fearing" <vik(at)postgresfriends(dot)org>, "PostgreSQL Hackers" <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: Catalog version access |
| Date: | 2021-02-22 00:27:29 |
| Message-ID: | 51eb5259-de4d-4bba-80a5-28f8f3e4fbe3@www.fastmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Sun, Feb 21, 2021, at 8:15 PM, Vik Fearing wrote:
> and a second patch that adds a read-only guc to get at it on the SQL
> level using SHOW catalog_version; or similar. I need that because I
> also do a dump of pg_settings and I would like for it to appear there.
The catalog version number is already available in pg_control_system().
postgres=# select * from pg_control_system();
-[ RECORD 1 ]------------+-----------------------
pg_control_version | 1300
catalog_version_no | 202007201
system_identifier | 6931867587550812316
pg_control_last_modified | 2021-02-21 20:59:06-03
--
Euler Taveira
EDB https://www.enterprisedb.com/
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2021-02-22 00:54:01 | Re: Catalog version access |
| Previous Message | Julien Rouhaud | 2021-02-21 23:57:30 | Re: Is a connection max lifetime useful in a connection pool? |