| From: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> |
|---|---|
| To: | Robert Haas <robertmhaas(at)gmail(dot)com> |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Josef Šimánek <josef(dot)simanek(at)gmail(dot)com>, Tomas Vondra <tomas(dot)vondra(at)enterprisedb(dot)com>, 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 01:39:14 |
| Message-ID: | CAKFQuwYPixWD48qHN62AFEdpaLSby-4L2Fweiv1jb6uMYrjOxw@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Wed, May 15, 2024 at 6:35 PM David G. Johnston <
david(dot)g(dot)johnston(at)gmail(dot)com> wrote:
>
> If in core I would still want to expose this as say a contrib module
> binary instead of hacking it into postgres. It would be our first server
> program entry there.
>
>
Sorry for self-reply but:
Maybe name it "pg_script_check" with a, for now mandatory, "--syntax-only"
option that enables this raw parse mode. Leaving room for executing this
in an environment where there is, or it can launch, a running instance that
then performs post-parse analysis as well.
David J.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Jonathan S. Katz | 2024-05-16 01:45:35 | PostgreSQL 17 Beta 1 release announcement draft |
| Previous Message | David G. Johnston | 2024-05-16 01:35:12 | Re: [PATCH] Add --syntax to postgres for SQL syntax checking |