Re: Append to a GUC parameter ?
От | David G Johnston |
---|---|
Тема | Re: Append to a GUC parameter ? |
Дата | |
Msg-id | 1407281676623-5813842.post@n5.nabble.com обсуждение исходный текст |
Ответ на | Re: Append to a GUC parameter ? (Alvaro Herrera <alvherre@2ndquadrant.com>) |
Ответы |
Re: Append to a GUC parameter ?
|
Список | pgsql-hackers |
Alvaro Herrera-9 wrote > Bruce Momjian wrote: >> On Tue, Aug 5, 2014 at 12:52:51PM -0700, Josh Berkus wrote: >> > On 08/05/2014 11:12 AM, Jerry Sievers wrote: >> > > shared_preload_libraries += auto_explain >> > > >> > > Would do the trick. >> > > >> > > I've never heard this mentioned before so presume not many have >> > > contemplated this. >> > >> > It's been discussed. >> > >> > However, other than shared_preload_libraries, I can't think of a GUC >> > which would benefit from this. Can you? >> >> search_path? > > Almost anything that's marked GUC_LIST_INPUT. A quick grep shows some > variables for which it doesn't make sense, such as DateStyle, and others > for which it would, such as temp_tablespaces, synchronous_standby_names, > listen_addresses, and the various preload_libraries params. Not sure > about log_destination. > > I think this merits a new GUC flag, say GUC_LIST_ADDITIVE. Would that allow, without any special syntax, multiple declarations of, say, shared_preload_libraries, to have their values appended instead of the most (or least, I forget which) recent one overwrite (or be ignored by) the existing value? The idea of requiring "+=" instead of just "=" is not particularly appealing... David J. -- View this message in context: http://postgresql.1045698.n5.nabble.com/Append-to-a-GUC-parameter-tp5813811p5813842.html Sent from the PostgreSQL - hackers mailing list archive at Nabble.com.
В списке pgsql-hackers по дате отправления: