Re: Doing better at HINTing an appropriate column within errorMissingColumn()
От | Andres Freund |
---|---|
Тема | Re: Doing better at HINTing an appropriate column within errorMissingColumn() |
Дата | |
Msg-id | 20140402201602.GV3750@awork2.anarazel.de обсуждение исходный текст |
Ответ на | Re: Doing better at HINTing an appropriate column within errorMissingColumn() (Greg Stark <stark@mit.edu>) |
Ответы |
Re: Doing better at HINTing an appropriate column within errorMissingColumn()
Re: Doing better at HINTing an appropriate column within errorMissingColumn() |
Список | pgsql-hackers |
On 2014-04-02 21:08:47 +0100, Greg Stark wrote: > Normally I'm not for adding gucs that just gate new features. But I think a > simple guc to turn this on or off would be fine and alleviate any concerns. > I think users would appreciate it quite a lot I don't have strong feelings about the feature, but introducing a guc for it feels entirely ridiculous to me. This is a minor detail in an error message, not more. > It would even have a positive effect of helping raise awareness of the > feature. I often scan the list of config options to get an idea of new > features when I'm installing new software or upgrading. Really? Should we now add GUCs for every feature then? Greetings, Andres Freund PS: Could you please start to properly quote again? You seem to have stopped doing that entirely in the last few months. -- Andres Freund http://www.2ndQuadrant.com/PostgreSQL Development, 24x7 Support, Training & Services
В списке pgsql-hackers по дате отправления: