On Fri, Jul 19, 2013 at 6:53 PM, Andres Freund <andres@2ndquadrant.com> wrote:
> So you can just do stuff like:
>
> server.foo.grand_unified_config = value.
>
it looks good to me too. when server parse values which is written in
postgresql.conf, server handles those parameter as item list value.
after that, those parameter overwrite to corresponding values. so, we
can allocate area of those values dynamically when server first parse
those values. (of cause we should count number of servers)
but I think that when server setting value is no set in order by
server name, parsing is a little difficult. we should check whether
server name has already registered at all time.
for example :
---- postgresql.conf -----
server.AAA.wal_sender_timeout = 60
server.BBB.synchronous_transfer = data_flush
server.AAA.synchronous_transfer = all
---- postgresql.conf -----
what do you think?
and if the parameter(e.g., wal_sender_timeout) is not set in
configure file(or postgresql,conf) like above, what value should we
set value to parameter? and how we handle originally
wal_sender_timeout? will it leave? or delete?
Regards,
-------
Sawada Masahiko