On 2018-03-26 22:44:09 +0200, Damir Simunic wrote:
> > *NONE* of the interesting problems are solved by HTTP2. You *still*
> > need a full blown protocol ontop of it. So no, this doesn't change that.
>
> If you had to nominate only one of those problems, which one would you consider the most interesting?
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
- annotate COMMIT, PREPARE TRANSACTION, COMMIT PREPARED with LSN of
associated WAL record
- have a less insane cancellation handling
- nested table support
Greetings,
Andres Freund
