| From: | Andres Freund <andres(at)2ndquadrant(dot)com> |
|---|---|
| To: | Greg Stark <stark(at)mit(dot)edu> |
| Cc: | Jim Nasby <jim(at)nasby(dot)net>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>, Robert Haas <robertmhaas(at)gmail(dot)com>, Peter Geoghegan <pg(at)heroku(dot)com>, Albe Laurenz <laurenz(dot)albe(at)wien(dot)gv(dot)at> |
| Subject: | Re: Doing better at HINTing an appropriate column within errorMissingColumn() |
| Date: | 2014-04-02 20:16:02 |
| Message-ID: | 20140402201602.GV3750@awork2.anarazel.de |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | 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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Peter Geoghegan | 2014-04-02 20:33:11 | Re: Doing better at HINTing an appropriate column within errorMissingColumn() |
| Previous Message | Greg Stark | 2014-04-02 20:08:47 | Re: Doing better at HINTing an appropriate column within errorMissingColumn() |