| From: | Andres Freund <andres(at)anarazel(dot)de> |
|---|---|
| To: | Robert Haas <robertmhaas(at)gmail(dot)com> |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, tushar <tushar(dot)ahuja(at)enterprisedb(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Create language syntax is not proper in pg_dumpall and not working using pg_upgrade |
| Date: | 2017-07-25 17:13:44 |
| Message-ID: | 20170725171344.jyuzfqzlpnsuaycw@alap3.anarazel.de |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 2017-07-25 13:10:11 -0400, Robert Haas wrote:
> On Tue, Jul 25, 2017 at 1:06 PM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> >> Is this assumption, like, documented someplace?
> >
> > Uh, right there?
>
> I don't think we can expect end-users to read the code comments to
> determine whether their apparently-legal SQL is fully supported.
I don't think plain end-users are going to create differently named PLs
using builtin handlers. There's plenty special casing of system object
in pg_dump and elsewhere. Dependency tracking doesn't quite work right
if you refer to system objects either, etc. This is superuser only
stuff, for a reason.
- Andres
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Robert Haas | 2017-07-25 17:18:25 | Re: Create language syntax is not proper in pg_dumpall and not working using pg_upgrade |
| Previous Message | Robert Haas | 2017-07-25 17:10:11 | Re: Create language syntax is not proper in pg_dumpall and not working using pg_upgrade |