| From: | Dimitri Fontaine <dimitri(at)2ndQuadrant(dot)fr> |
|---|---|
| To: | David Fetter <david(at)fetter(dot)org> |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Andrew Dunstan <andrew(at)dunslane(dot)net>, Magnus Hagander <magnus(at)hagander(dot)net>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: Should we get rid of custom_variable_classes altogether? |
| Date: | 2011-10-03 19:21:43 |
| Message-ID: | m2d3ed6fug.fsf@2ndQuadrant.fr |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
David Fetter <david(at)fetter(dot)org> writes:
> Perhaps it's best to document this usage and include the warning for
> those less "bright," as you term them. I'd be less tempted to call
> them "not bright" and more tempted to think they might assume
> PostgreSQL already takes care of cleaning this up, but whatever.
Who's that dim? D'oh.
Another compromise might be to allow for defining variable in any class
from the configuration files but restrict that to existing classes from
the SET command. Wait, that's exactly what happens as soon as there's
no explicit custom_variable_classes, right?
So we're talking about people with configuration file editing and reload
powers, not about anyone who can connect. I think that's ok.
Regards,
--
Dimitri Fontaine
http://2ndQuadrant.fr PostgreSQL : Expertise, Formation et Support
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Robert Haas | 2011-10-03 19:40:12 | Re: Bug with pg_ctl -w/wait and config-only directories |
| Previous Message | Bruce Momjian | 2011-10-03 19:09:47 | Re: Bug with pg_ctl -w/wait and config-only directories |