Re: Proposal: http2 wire format

From: Tatsuo Ishii <ishii(at)sraoss(dot)co(dot)jp>
To: andres(at)anarazel(dot)de
Cc: damir(dot)simunic(at)wa-research(dot)ch, tgl(at)sss(dot)pgh(dot)pa(dot)us, sitnikov(dot)vladimir(at)gmail(dot)com, pgsql-hackers(at)postgresql(dot)org
Subject: Re: Proposal: http2 wire format
Date: 2018-03-28 08:39:32
Views: Raw Message | Whole Thread | Download mbox | Resend email
Lists: pgsql-hackers

> A few random, very tired, points:
> - consolidated message for common tasks:
> - (bind, [describe?,] execute) to reduce overhead of prepared
> statement execution (both in messages, as well as branches)
> - (anonymous parse, bind, describe, execute) to make it cheaper to
> send statements with out-of-line parameters
> - get rid of length limits of individual fields, probably w/ some variable
> length encoding (simple 7 bit?)
> - allow *streaming* of large datums
> - type-level decisions about binary type transport, right now it's a lot
> of effort (including potentially additional roundtrips), to get the
> few important types to be transported in binary fashion. E.g. floating
> points are really expensive to stringify, bytea as text gets a lot
> bigger etc, but a lot of other types don't benefit a lot
> associated WAL record
> - have a less insane cancellation handling
> - nested table support

I would like to have portal/statement name to be added to response
messages (i.e. parse complete, bind complete, close complete, and
command complete.). Currently it's not easy to recognize which
response corresponds to which message, which makes certain
applications such as Pgpool-II hard to implement and inefficient.

Best regards,
Tatsuo Ishii
SRA OSS, Inc. Japan

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Aleksander Alekseev 2018-03-28 09:21:15 Re: new function for tsquery creartion
Previous Message Teodor Sigaev 2018-03-28 08:35:06 Re: Cast jsonb to numeric, int, float, bool