Subject: Re: Jsonb transform for pl/python
To: Anthony Bykov <a.bykov@postgrespro.ru>
References: <20171025145100.3a19933f@anthony-24-g082ur>
 <20171113130028.32405fee@anthony-24-g082ur>
 <20171113150816.1377.17052.pgcf@coridan.postgresql.org>
 <20171120123555.546c922f@anthony-24-g082ur>
 <20171120134835.GA9855@e733.localdomain>
 <20171206144054.5664c119@anthony-24-g082ur>
 <881aea8c-23a4-0694-8182-72620afe84c4@2ndquadrant.com>
 <20171211112206.3b4ea92f@anthony-24-g082ur>
Cc: pgsql-hackers@lists.postgresql.org
From: Peter Eisentraut <peter.eisentraut@2ndquadrant.com>
Organization: 2ndQuadrant
Message-ID: <c1ea3dfc-c383-b820-1798-39de0a514c2b@2ndquadrant.com>
Date: Mon, 11 Dec 2017 16:16:58 -0500
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.13; rv:52.0)
 Gecko/20100101 Thunderbird/52.5.0
MIME-Version: 1.0
In-Reply-To: <20171211112206.3b4ea92f@anthony-24-g082ur>
Content-Type: text/plain; charset=utf-8
Content-Language: en-US
Content-Transfer-Encoding: 7bit
Precedence: bulk

On 12/11/17 03:22, Anthony Bykov wrote:
>> Why not make this part of the plpythonu extension?  It doesn't have to
>> be a separate contrib module.
>>
> Hello,
> I thought about that, but the problem is that there will be no
> possibilities to create custom transform if we create this extension by
> default.

OK, could it be a separate extension, but part of the same code directory?

-- 
Peter Eisentraut              http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services