Re: Extensibility of the PostgreSQL wire protocol

Peter Eisentraut <peter.eisentraut@enterprisedb.com>

From: Peter Eisentraut <peter.eisentraut@enterprisedb.com>
To: Jan Wieck <jan@wi3ck.info>, Kuntal Ghosh <kuntalghosh.2007@gmail.com>
Cc: Dave Cramer <davecramer@postgres.rocks>, Robert Haas <robertmhaas@gmail.com>, Tom Lane <tgl@sss.pgh.pa.us>, "Jonah H. Harris" <jonah.harris@gmail.com>, PostgreSQL Hackers <pgsql-hackers@lists.postgresql.org>
Date: 2021-03-03T19:43:20Z
Lists: pgsql-hackers
I think, the way the abstractions are chosen in this patch, it is still 
very much tied to how the libpq protocol works.  For example, there is a 
cancel key and a ready-for-query message.  Some of the details of the 
simple and the extended query are exposed.  So you could create a 
protocol that has a different way of encoding the payloads, as your 
telnet example does, but I don't believe that you could implement a 
competitor's protocol through this.  Unless you have that done and want 
to show it?