| From: | Peter Eisentraut <peter(dot)eisentraut(at)enterprisedb(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org> |
| Cc: | Swaha Miller <swaha(dot)miller(at)gmail(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: support for CREATE MODULE |
| Date: | 2022-02-07 15:54:29 |
| Message-ID: | fdcf353a-c922-7727-96af-2273d25af80d@enterprisedb.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 04.02.22 23:12, Tom Lane wrote:
> Right. We've looked into that before --- when I made pg_namespace,
> I called it that because I thought we might be able to support
> nested namespaces --- but it'd really create a mess. In particular,
> the SQL standard says what a three-part name means, and this ain't it.
Modules are part of the SQL standard, so there is surely some
name-resolution system specified there as well.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Peter Eisentraut | 2022-02-07 15:59:48 | Re: Documentation about PL transforms |
| Previous Message | Esteban Zimanyi | 2022-02-07 15:52:22 | Re: Storage for multiple variable-length attributes in a single row |