| From: | Andres Freund <andres(at)2ndquadrant(dot)com> |
|---|---|
| To: | Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com> |
| Cc: | PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: [RFC] Extend namespace of valid guc names |
| Date: | 2013-02-25 21:34:00 |
| Message-ID: | 20130225213400.GF3849@awork2.anarazel.de |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 2013-02-25 22:27:21 +0100, Pavel Stehule wrote:
> Why?
The concrete usecase is having some form of nesting available for a
shared_library.
shared_preload_libraries = 'bdr'
bdr.connections = 'a, b'
bdr.a.dsn = '...'
bdr.a.xxx = '...'
bdr.b.dsn = '...'
> There are no multilevels structures in pg. Variables should be joined
> with schemas or extensions. Other levels are messy.
So? What does the one existing level SQL have to do with
postgresql.conf? And why is it messy?
Not that as I said before
SET foo.bar.blub = '1'; currently is already allowed.
Greetings,
Andres Freund
--
Andres Freund http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andrew Dunstan | 2013-02-25 21:50:54 | Re: [RFC] Extend namespace of valid guc names |
| Previous Message | Pavel Stehule | 2013-02-25 21:27:21 | Re: [RFC] Extend namespace of valid guc names |