| From: | Jan Wieck <jan(at)wi3ck(dot)info> |
|---|---|
| To: | Magnus Hagander <magnus(at)hagander(dot)net> |
| Cc: | Jacob Champion <pchampion(at)vmware(dot)com>, "ishii(at)sraoss(dot)co(dot)jp" <ishii(at)sraoss(dot)co(dot)jp>, "pgsql-hackers(at)lists(dot)postgresql(dot)org" <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: PROXY protocol support |
| Date: | 2021-03-04 21:01:15 |
| Message-ID: | 139db8b3-48dd-95f1-e4ee-07b85edc3c33@wi3ck.info |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 3/4/21 3:40 PM, Magnus Hagander wrote:
> On Thu, Mar 4, 2021 at 9:29 PM Jan Wieck <jan(at)wi3ck(dot)info> wrote:
>> This looks like it would only need a few extra protocol messages to be
>> understood by the backend. It might be possible to implement that with
>> the loadable wire protocol extensions proposed here:
>>
>> https://commitfest.postgresql.org/32/3018/
>
> Actually the whole point of it is that it *doesn't* need any new
> protocol messages. And that it *wraps* whatever is there, definitely
> doesn't replace it. It should equally be wrapping whatever an
> extension uses.
>
> So while the base topic is not unrelated, I don't think there is any
> overlap between these.
I might be missing something here, but isn't sending some extra,
informational *header*, which is understood by the backend, in essence a
protocol extension?
Regards, Jan
--
Jan Wieck
Principle Database Engineer
Amazon Web Services
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Alvaro Herrera | 2021-03-04 21:04:03 | Re: CI/windows docker vs "am a service" autodetection on windows |
| Previous Message | Tom Lane | 2021-03-04 21:00:36 | Re: Huge memory consumption on partitioned table with FKs |