| From: | "Jonah H(dot) Harris" <jonah(dot)harris(at)gmail(dot)com> |
|---|---|
| To: | Jan Wieck <jan(at)wi3ck(dot)info> |
| Cc: | pgsql-hackers(at)lists(dot)postgresql(dot)org |
| Subject: | Re: Extensibility of the PostgreSQL wire protocol |
| Date: | 2021-01-25 15:18:45 |
| Message-ID: | CADUqk8W0QZuMxfYn+vpmGUHAeHh9PUdBnOQkbNiS=1jFipgiTw@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Mon, Jan 25, 2021 at 10:07 AM Jan Wieck <jan(at)wi3ck(dot)info> wrote:
> The following is a request for discussion and comments, not a refined
> proposal accompanied by a working patch.
>
After implementing this three different ways inside the backend over the
years, I landed on almost this identical approach for handling the MySQL,
TDS, MongoDB, and Oracle protocols for NEXTGRES.
Initially, each was implemented as an background worker extension which had
to handle its own networking, passing the fd off to new protocol-specific
connections, etc. This worked, but duplicate a good amount of logic. It
would be great to have a standard, loadable, way to add support for a new
protocol.
--
Jonah H. Harris
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Alexander Korotkov | 2021-01-25 15:24:52 | Re: Phrase search vs. multi-lexeme tokens |
| Previous Message | Bharath Rupireddy | 2021-01-25 15:12:39 | Re: [PATCH] postgres_fdw connection caching - cause remote sessions linger till the local session exit |