| From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
|---|---|
| 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 15:13:55 |
| Message-ID: | CA+Tgmoa1WvAVEqpM-A-WvGKmyaV3YJ9krEBGLLgkiqJFS0j8qw@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Mon, Oct 3, 2011 at 10:55 AM, David Fetter <david(at)fetter(dot)org> wrote:
> 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.
Yeah. custom_variable_classes is a pretty annoying wart, but if it's
set to the default value (namely, empty) then it actually does prevent
people from setting bajillions of completely pointless settings, which
seems like it has some merit. I'm not sure it has enough merit to
justify keeping it around, but it has more than none. We could allow
entering a date of February 31st, too, but we don't.
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Robert Haas | 2011-10-03 15:16:06 | Re: [v9.2] DROP statement reworks |
| Previous Message | Robert Haas | 2011-10-03 15:04:31 | Re: pg_dump issues |