Re: [PATCH] Add transforms feature

From: Robert Haas <robertmhaas(at)gmail(dot)com>
To: Peter Eisentraut <peter_e(at)gmx(dot)net>
Cc: Dimitri Fontaine <dimitri(at)2ndquadrant(dot)fr>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: [PATCH] Add transforms feature
Date: 2013-12-11 12:40:35
Message-ID: CA+TgmoZQHB7=_WDiQ73Mt48KoLY68ycpBtSt6mq1bt9prSE-8Q@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Tue, Dec 10, 2013 at 10:35 PM, Peter Eisentraut <peter_e(at)gmx(dot)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

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Andres Freund 2013-12-11 12:41:43 should we add a XLogRecPtr/LSN SQL type?
Previous Message Greg Stark 2013-12-11 12:23:26 Re: ANALYZE sampling is too good