| From: | Julien Rouhaud <rjuju123(at)gmail(dot)com> |
|---|---|
| To: | Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com> |
| Cc: | Joel Jacobson <joel(at)compiler(dot)org>, Vik Fearing <vik(at)postgresfriends(dot)org>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Andrew Dunstan <andrew(at)dunslane(dot)net>, Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: Idea: Avoid JOINs by using path expressions to follow FKs |
| Date: | 2021-03-30 06:52:47 |
| Message-ID: | 20210330065247.z6ciai3nzqj2argo@nol |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Tue, Mar 30, 2021 at 08:03:09AM +0200, Pavel Stehule wrote:
>
> On second hand, it can be very nice to have some special strict mode in
> Postgres - maybe slower, not compatible, that disallow some dangerous or
> unsafe queries. But it is possible to solve in extensions, but nobody did
> it. Something like plpgsql_check for SQL - who will write sql_check?
The #1 cause of problems is probably unqualified outer references, and
unfortunately I don't think it's really possible to detect that in an
extension, as the required information is only available in the raw parsetree.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Pavel Stehule | 2021-03-30 07:02:39 | Re: Idea: Avoid JOINs by using path expressions to follow FKs |
| Previous Message | Michael Paquier | 2021-03-30 06:50:28 | Re: Refactor SSL test framework to support multiple TLS libraries |