From: | Serge Rielau <serge(at)rielau(dot)com> |
---|---|
To: | Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com> |
Cc: | Craig Ringer <craig(at)2ndquadrant(dot)com>, Wolfgang Wilhelm <wolfgang20121964(at)yahoo(dot)de>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Packages: Again |
Date: | 2017-01-13 19:38:49 |
Message-ID: | 84BEB3BF-D70E-4913-98ED-C92F59EFE7DE@rielau.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
> On Jan 13, 2017, at 11:11 AM, Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com> wrote:
>
> With Postgres we should to think much more about other PL - there is not only PL/pgSQL. So any what we create should be available for any PL. Our PLpgSQL is based on total different technology design - so some benefits of sharing compiled code across databases has not too value in Postgres.
Let me stress one last point:
MODULE’s are 100% orthogonal to PLpgSQL as implement by SFDC and also orthogonal to SQL PL as implemented by DB2.
Modules can (and do for us) contain C-functions of example.
Similarly when the community provides provides server side session variables I have no doubt they will integrate with MODULE’s with very little work.
It’s a DDL and name resolution game, predominantly
Cheers
Serge
From | Date | Subject | |
---|---|---|---|
Next Message | Alvaro Herrera | 2017-01-13 20:09:57 | Re: [COMMITTERS] pgsql: Fix a bug in how we generate partition constraints. |
Previous Message | Robert Haas | 2017-01-13 19:35:25 | Re: [COMMITTERS] pgsql: Fix a bug in how we generate partition constraints. |