From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
---|---|
To: | Peter Eisentraut <peter_e(at)gmx(dot)net> |
Cc: | Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com>, Michael Paquier <michael(dot)paquier(at)gmail(dot)com>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: [PATCH] Add transforms feature |
Date: | 2015-03-17 15:52:48 |
Message-ID: | CA+Tgmoa7kVGdrFg2s29sp8TgZQzr=rfTq3kaJRq2bfn+AMSNKQ@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Mon, Mar 16, 2015 at 9:51 PM, Peter Eisentraut <peter_e(at)gmx(dot)net> wrote:
>> 4. Why guc-use-transforms? Is there some possible negative side effect
>> of transformations, so we have to disable it? If somebody don't would to
>> use some transformations, then he should not to install some specific
>> transformation.
>
> Well, there was extensive discussion last time around where people
> disagreed with that assertion.
I think we need to the ability to control it per-function, but having
a global disabling knob on top of that doesn't seem especially useful.
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
From | Date | Subject | |
---|---|---|---|
Next Message | Bruce Momjian | 2015-03-17 16:47:07 | Re: Rethinking the parameter access hooks for plpgsql's benefit |
Previous Message | Robert Haas | 2015-03-17 15:50:28 | Re: PATCH: pgbench - merging transaction logs |