Re: proposal, patch: allow multiple plpgsql plugins

From: Marko Tiikkaja <marko(at)joh(dot)to>
To: Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Subject: Re: proposal, patch: allow multiple plpgsql plugins
Date: 2014-01-12 16:33:48
Message-ID: 52D2C3EC.6080609@joh.to
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 1/9/14, 11:41 PM, Pavel Stehule wrote:
> There are two basic questions:
>
> b) will we support same API still - a reference on plugin_info in exec
> state is a issue - described in patch.

Pardon my ignorance, but why does the plugin_info have to be in the
executor state? If we're going to change the API, can't we pass it
directly to the callback function? Am I missing something completely
obvious? :-)

Regards,
Marko Tiikkaja

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Marko Tiikkaja 2014-01-12 16:48:01 Re: proposal, patch: allow multiple plpgsql plugins
Previous Message Kevin Grittner 2014-01-12 16:28:57 ECPG regression tests generating warnings