| From: | Michael Paquier <michael(at)paquier(dot)xyz> |
|---|---|
| To: | "Bossart, Nathan" <bossartn(at)amazon(dot)com> |
| Cc: | Bharath Rupireddy <bharath(dot)rupireddyforpostgres(at)gmail(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Justin Pryzby <pryzby(at)telsasoft(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: should we document an example to set multiple libraries in shared_preload_libraries? |
| Date: | 2021-12-03 01:02:56 |
| Message-ID: | YalswMVTu2UKAp+Q@paquier.xyz |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Fri, Dec 03, 2021 at 12:45:56AM +0000, Bossart, Nathan wrote:
> I think the problems you noted upthread are shared for all GUCs with
> type GUC_LIST_QUOTE (e.g., search_path, temp_tablespaces). Perhaps
> the documentation for each of these GUCs should contain a short blurb
> about how to properly SET a list of values.
Yeah, the approach taken by the proposed patch is not going to scale
and age well.
It seems to me that we should have something dedicated to lists around
the section for "Parameter Names and Values", and add a link in the
description of each parameters concerned back to the generic
description.
> Also upthread, I see that you gave the following example for an
> incorrect way to set shared_preload_libraries:
>
> ALTER SYSTEM SET shared_preload_libraries =
> auth_delay,pg_stat_statements,sepgsql; --> wrong
>
> Why is this wrong? It seems to work okay for me.
Yep.
--
Michael
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Michael Paquier | 2021-12-03 01:06:47 | Re: GUC flags |
| Previous Message | Michael Paquier | 2021-12-03 00:53:22 | Re: Skip vacuum log report code in lazy_scan_heap() if possible |