Re: should we document an example to set multiple libraries in shared_preload_libraries?

From: "Bossart, Nathan" <bossartn(at)amazon(dot)com>
To: Bharath Rupireddy <bharath(dot)rupireddyforpostgres(at)gmail(dot)com>, "Michael Paquier" <michael(at)paquier(dot)xyz>
Cc: 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 17:55:04
Message-ID: DBC642C1-A3D3-40F0-A17D-18F49E0F4F76@amazon.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 12/3/21, 6:21 AM, "Bharath Rupireddy" <bharath(dot)rupireddyforpostgres(at)gmail(dot)com> wrote:
> +1 to add here in the "Parameter Names and Values section", but do we
> want to backlink every string parameter to this section? I think it
> needs more effort. IMO, we can just backlink for
> shared_preload_libraries alone. Thoughts?

IMO this is most important for GUC_LIST_QUOTE parameters, of which
there are only a handful. I don't think adding a link to every string
parameter is necessary.

Nathan

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2021-12-03 18:09:31 Re: pg_dump versus ancient server versions
Previous Message Bossart, Nathan 2021-12-03 17:46:51 Re: Skip vacuum log report code in lazy_scan_heap() if possible