Re: Should we get rid of custom_variable_classes altogether?

Robert Haas <robertmhaas@gmail.com> writes:
> 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.

Well, that argument was essentially why we put it in to begin with.
But I think pretty much everybody agrees that it's more trouble than
it's worth (in fact, weren't you one of the people complaining about
it?)

			regards, tom lane