Thanks !
Cheers,
Rémi-C
2016-03-05 0:38 GMT+01:00 Adrian Klaver :
> On 03/04/2016 01:46 AM, Rémi Cura wrote:
>
>> Thanks for the answer guys.
>>
>> I should have mentionned that I had read the doc,
>> and was looking for non explicit knowledge,
>> like :
>> - what is
On 03/04/2016 01:46 AM, Rémi Cura wrote:
Thanks for the answer guys.
I should have mentionned that I had read the doc,
and was looking for non explicit knowledge,
like :
- what is the reputation of plpython for a dba?
- are there actual production system that use it
- what would be the
On 4 March 2016 at 10:46, Rémi Cura wrote:
> Thanks for the answer guys.
>
> I should have mentionned that I had read the doc,
> and was looking for non explicit knowledge,
> like :
> - what is the reputation of plpython for a dba?
>
Dunno.
- are there actual production
Thanks for the answer guys.
I should have mentionned that I had read the doc,
and was looking for non explicit knowledge,
like :
- what is the reputation of plpython for a dba?
- are there actual production system that use it
- what would be the recommended usage perimeter ?
(only
On Thu, Mar 3, 2016 at 12:35 PM, Adrian Klaver
wrote:
> On 03/03/2016 10:09 AM, Rémi Cura wrote:
>
>> Hey List,
>>
>> would it be considered safe to use plpythonu for a production database?
>> What would be the limitations/ dangers?
>>
>
> They are explained here:
>
>
On 03/03/2016 10:09 AM, Rémi Cura wrote:
Hey List,
would it be considered safe to use plpythonu for a production database?
What would be the limitations/ dangers?
They are explained here:
http://www.postgresql.org/docs/9.5/interactive/plpython.html
"PL/Python is only available as an
Hey List,
would it be considered safe to use plpythonu for a production database?
What would be the limitations/ dangers?
Thanks,
Cheers,
Rémi-C