From: | Jan Wieck <jan(at)wi3ck(dot)info> |
---|---|
To: | "Jonah H(dot) Harris" <jonah(dot)harris(at)gmail(dot)com> |
Cc: | pgsql-hackers(at)lists(dot)postgresql(dot)org |
Subject: | Re: Extensibility of the PostgreSQL wire protocol |
Date: | 2021-01-25 17:17:58 |
Message-ID: | CAGBW59e2Xj_dNE5ruSZrZqz0t2kn+uj1sUMp=ttSk4tx3fqFzg@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Hi Jonah,
On Mon, Jan 25, 2021 at 10:18 AM Jonah H. Harris <jonah(dot)harris(at)gmail(dot)com>
wrote:
> 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.
>
Could any of that be open sourced? It would be an excellent addition to add
one of those as example code.
Regards, Jan
>
> 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
>
>
--
Jan Wieck
From | Date | Subject | |
---|---|---|---|
Next Message | Heikki Linnakangas | 2021-01-25 17:28:33 | Snapbuild woes followup |
Previous Message | Robert Haas | 2021-01-25 17:14:42 | Re: ResourceOwner refactoring |