On Wed, Jun 21, 2017 at 12:15 PM, Robert Haas <robertmh...@gmail.com> wrote: > I think the problem is real, > but I'm not sure that this is the best solution. On the other hand, > I'm also not entirely sure I understand the proposal yet.
Given the problems with changing the protocol it does seem like generalizing away from "connection id" to "arbitrary payload" would be useful. Like, add a new "attachment map" area where any application-aware node that encounters the message can attach data. If some node further downstream sends a response message the contents of the attachment map would be sent back as-is. The advantage of "connection id" is that the messages are still of fixed size whereas the more flexible arrangement would necessitate that message sizes vary. In return middleware gets a place to store session information that can be used more broadly than a simple externally generated connection id. David J. -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
