| From: | Jan Wieck <jan(at)wi3ck(dot)info> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Robert Haas <robertmhaas(at)gmail(dot)com> |
| Cc: | PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: Extensibility of the PostgreSQL wire protocol |
| Date: | 2021-02-22 16:44:52 |
| Message-ID: | 56a85230-4557-c987-5260-3eb0dab39e92@wi3ck.info |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 2/10/21 1:10 PM, Tom Lane wrote:
> What I'm actually more concerned about, in this whole line of development,
> is the follow-on requests that will surely occur to kluge up Postgres
> to make its behavior more like $whatever. As in "well, now that we
> can serve MySQL clients protocol-wise, can't we pretty please have a
> mode that makes the parser act more like MySQL".
Those requests will naturally follow. But I don't see it as the main
project's responsibility to satisfy them. It would be rather natural to
develop the two things together. The same developer or group of
developers, who are trying to connect a certain client, will want to
have other compatibility features.
As Jim Mlodgenski just posted in [0], having the ability to also extend
and/or replace the parser will give them the ability to do just that.
Regards, Jan
--
Jan Wieck
Principle Database Engineer
Amazon Web Services
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Justin Pryzby | 2021-02-22 17:15:25 | Re: [PATCH]: Allow errors in parameter values to be reported during the BIND phase itself.. |
| Previous Message | Muhammad Usama | 2021-02-22 16:44:03 | Re: [PATCH] Feature improvement for TRUNCATE tab completion. |