| From: | Peter Eisentraut <peter(at)eisentraut(dot)org> |
|---|---|
| To: | Robert Haas <robertmhaas(at)gmail(dot)com>, Josef Šimánek <josef(dot)simanek(at)gmail(dot)com> |
| Cc: | Tomas Vondra <tomas(dot)vondra(at)enterprisedb(dot)com>, "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: [PATCH] Add --syntax to postgres for SQL syntax checking |
| Date: | 2024-05-16 10:29:08 |
| Message-ID: | 84fb3001-d9ee-49f4-9b01-5e4358d59b3a@eisentraut.org |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 15.05.24 21:05, Robert Haas wrote:
> I don't think it's at all obvious that this belongs on the server side
> rather than the client side. I think it could be done in either place,
> or both. I just think we don't have the infrastructure to do it
> cleanly, at present.
I think if you're going to do a syntax-check-with-catalog-lookup mode,
you need authentication and access control. The mode without catalog
lookup doesn't need that. But it might be better to offer both modes
through a similar interface (or at least plan ahead for that).
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Jelte Fennema-Nio | 2024-05-16 10:41:50 | Re: PostgreSQL 17 Beta 1 release announcement draft |
| Previous Message | Peter Eisentraut | 2024-05-16 10:07:32 | Re: An improved README experience for PostgreSQL |