On Tue, Dec 10, 2013 at 10:35 PM, Peter Eisentraut <pete...@gmx.net> wrote: > On Fri, 2013-12-06 at 11:28 +0100, Dimitri Fontaine wrote: >> > Here is an idea. Add a GUC that basically says something like >> > use_transforms = on|off. You can then attach that to individual >> > functions, which is the right granularity, because only the function >> > knows whether its code expects transforms or not. But you can use >> the >> > full power of GUC to configure it any way you want. > > Here is an updated patch that implements this, makes some of the > documentation improvements that you suggested, and rebases everything.
I'm still kinda unimpressed by this. Behavior-changing GUC, uggh. -- Robert Haas EnterpriseDB: http://www.enterprisedb.com The Enterprise PostgreSQL Company -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
