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 18:35:56 |
Message-ID: | 3ECC3C9C-D94F-47DF-B578-909DD1928C23@rielau.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
> On Jan 13, 2017, at 10:23 AM, Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com> wrote:
>
> I have not clean feeling from this - I am pretty sure so I am afraid schizophrenic between MODULES, SCHEMAS. Nested schemas increase complexity of searching complexity and breaks a logic database.schema.object
Yes my proposal to nest schemata is “radical” and this community is not falling into that camp.
But there is nothing holy about database.schema.object.attribute
.
>
> Currently almost all in PostgreSQL PL design is primitive, but that means pretty simple too.
We are having > 30,000 functions with a total of millions of lines of code.
You are describing a self fulfilling prophecy here.
As long as the community codebase only caters to its existing users you will not see a change in the usage pattern of the base.
> It is hard to see a advantages of this proposal.
At least I tried :-)
Serge
From | Date | Subject | |
---|---|---|---|
Next Message | Robert Haas | 2017-01-13 18:37:58 | pgsql: Fix cardinality estimates for parallel joins. |
Previous Message | Pavel Stehule | 2017-01-13 18:23:01 | Re: Packages: Again |