Re: Proposal: http2 wire format

> On 26 Mar 2018, at 15:42, Alvaro Hernandez <aht(at)ongres(dot)com> wrote:
>
>
>
> On 26/03/18 13:11, Damir Simunic wrote:
>>> On 26 Mar 2018, at 11:13, Vladimir Sitnikov <sitnikov(dot)vladimir(at)gmail(dot)com <mailto:sitnikov(dot)vladimir(at)gmail(dot)com>> wrote:
>>>
>>> Damir> * What are the criteria for getting this into the core?
>>> Craig>Mine would be:
>>>
>>> +1
>>>
>>> There's a relevant list as well: https://github.com/pgjdbc/pgjdbc/blob/master/backend_protocol_v4_wanted_features.md <https://github.com/pgjdbc/pgjdbc/blob/master/backend_protocol_v4_wanted_features.md>
>>>
>>
>> This is a great addition to the list, thanks!
>>
>> Damir
>>
>
> Hi Damir.
>
> I'm interested in the idea. However, way before writing a PoC, IMVHO I'd rather write a detailed document including:
>
> - A brief summary of the main features of HTTP2 and why it might be a good fit for PG (of course there's a lot of doc in the wild about HTTP/2, so just a summary of the main relevant features and an analysis of how it may fit Postgres).
>
> - A more or less thorough description of how every feature in current PostgreSQL protocol would be implemented on HTTP/2.
>
> - Similar to the above, but applied to the v4 TODO feature list.
>
> - A section for connection poolers, as an auth, as these are very important topics.
>
>
> Hope this helps,
>
> Álvaro
>

Álvaro, it does help, thanks. This discussion is to inform such a document. But the topic is such that having a good PoC will move the discussion further much faster.

Can you help with thinking about how would HTTP2 impact connection poolers, I don’t know much about those?
> --
>
> Alvaro Hernandez
>
>
> -----------
> OnGres