Re: Patch for 8.5, transformationHook

From: Peter Eisentraut <peter_e(at)gmx(dot)net>
To: pgsql-hackers(at)postgresql(dot)org
Cc: Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Subject: Re: Patch for 8.5, transformationHook
Date: 2009-04-20 14:16:38
Message-ID: 200904201716.38801.peter_e@gmx.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: 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.

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2009-04-20 14:38:02 Re: Re: [COMMITTERS] pgsql: Explicitly bind gettext to the correct encoding on Windows.
Previous Message Tom Lane 2009-04-20 14:14:01 Re: [PATCH] unalias of ACL_SELECT_FOR_UPDATE