From: Tom Lane <tgl@sss.pgh.pa.us>
To: Peter Galbavy <peter.galbavy@knowtion.net>
Cc: pgsql-hackers@postgreSQL.org
Cc: pgsql-interfaces@postgreSQL.org
Subject: Re: More thoughts about FE/BE protocol
Date: Thu, 10 Apr 2003 09:57:41 -0400
Message-ID: <3625.1049983061@sss.pgh.pa.us> (raw)
In-Reply-To: <003f01c2ff40$9f1a0e70$7c28a8c0@cblan.mblox.com>
References: <10478.1049927451@sss.pgh.pa.us>
<003f01c2ff40$9f1a0e70$7c28a8c0@cblan.mblox.com>
"Peter Galbavy" <peter.galbavy@knowtion.net> writes:
> Is there any message - speaking from a standpoint of a normal user and not a
> source hacker WRT postgresql - where knowing the length of the response is
> either unknown or is expensive (in buffering) to find out ?
See my response to ljb --- I think that in practice people assemble each
message before sending anyway. If you don't do it that way, you've got
a problem with recovering if you hit an error condition after sending a
partial message.
regards, tom lane
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-interfaces@postgresql.org
Cc: tgl@sss.pgh.pa.us, peter.galbavy@knowtion.net, pgsql-hackers@postgreSQL.org
Subject: Re: More thoughts about FE/BE protocol
In-Reply-To: <3625.1049983061@sss.pgh.pa.us>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox