Re: Patch for 8.5, transformationHook - Mailing list pgsql-hackers

From Peter Eisentraut
Subject Re: Patch for 8.5, transformationHook
Date
Msg-id 200904201716.38801.peter_e@gmx.net
Whole thread Raw
In response to Re: Patch for 8.5, transformationHook  (Pavel Stehule <pavel.stehule@gmail.com>)
Responses Re: Patch for 8.5, transformationHook  (Tom Lane <tgl@sss.pgh.pa.us>)
Re: Patch for 8.5, transformationHook  (Pavel Stehule <pavel.stehule@gmail.com>)
List pgsql-hackers
On Monday 20 April 2009 09:52:05 Pavel Stehule wrote:
> I don't believe so is possible to find other general solution. (or
> better I didn't find any other solution). Tom has true,
> transformationHook on expression is expensive. I thing, so hook on
> function should be simple and fast - not all transformation's should
> be simple defined via property - classic sample is "decode" like
> functions, it needs procedural code.

I find this all a bit premature, given that you haven't clearly defined what 
sort of user-visible functionality you hope to end up implementing.  Which 
makes it hard to argue why this or that approach might be better.


pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: [PATCH] unalias of ACL_SELECT_FOR_UPDATE
Next
From: Tom Lane
Date:
Subject: Re: Re: [COMMITTERS] pgsql: Explicitly bind gettext to the correct encoding on Windows.