From: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> |
---|---|
To: | Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com> |
Cc: | pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: list append syntax for postgresql.conf |
Date: | 2019-02-20 15:59:28 |
Message-ID: | CAKFQuwZVgykzf+Stvt+gYOx4PYBtNWKOFLQi3hHPcVteOmMxkw@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Wednesday, February 20, 2019, Peter Eisentraut <
peter(dot)eisentraut(at)2ndquadrant(dot)com> wrote:
> Nowadays there are a number of methods for composing multiple
> postgresql.conf files for modularity. But if you have a bunch of things
> you want to load via shared_preload_libraries, you have to put them all
> in one setting. How about some kind of syntax for appending something
> to a list, like
>
> shared_preload_libraries += 'pg_stat_statements'
>
I would rather just have the behavior for that variable “append mode”,
period. Maybe do it generally for all multi-value variables. It would be
like “add only” permissions - if you don’t want something loaded it cannot
be specified ever, overwrite is not allowed. Get rid of any
order-of-operations concerns.
David J.
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2019-02-20 16:03:32 | Re: Delay locking partitions during INSERT and UPDATE |
Previous Message | Joe Conway | 2019-02-20 15:54:50 | Re: list append syntax for postgresql.conf |