| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Durumdara <durumdara(at)gmail(dot)com> |
| Cc: | Postgres General <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: CRL reloading info - is it refreshed? |
| Date: | 2020-09-21 18:11:00 |
| Message-ID: | 990633.1600711860@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
Durumdara <durumdara(at)gmail(dot)com> writes:
> What will happen when onfly reload finds something bad (99% of the config
> is good, but 1 line in in the config file is wrong)?
For a CRL file, the file will be ignored and the old configuration will
remain, I believe.
> And the most important question: how do we know that PG 11 reloaded the
> CRL?
> Is there any way to get the last full reload timestamp value, or the
> version of the actual CRL file, or something like that?
There's pg_conf_load_time(), but it doesn't go down to the level of
detail of which specific settings were updated.
The short answer to all these concerns is "after a SIGHUP, look in the
postmaster log to see if there were any complaints".
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Niels Jespersen | 2020-09-22 10:22:58 | SV: Foreign tables, user mappings and privilege setup |
| Previous Message | Joshua Drake | 2020-09-21 17:53:08 | Re: Can I get some PostgreSQL developer feedback on these five general issues I have with PostgreSQL and its ecosystem? |