Thread: pgsql: Add some code to ensure that we don't lose communication sync due

Log Message:
-----------
Add some code to ensure that we don't lose communication sync due to
an oversize message, per suggestion from Oliver Jowett.  I'm a bit
dubious that this is a real problem, since the client likely doesn't
have any more space available than the server, but it's not hard to
make it behave according to the protocol intention.

Modified Files:
--------------
    pgsql/src/backend/libpq:
        pqcomm.c (r1.172 -> r1.173)
        (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/backend/libpq/pqcomm.c.diff?r1=1.172&r2=1.173)

On Tue, 19 Oct 2004, Tom Lane wrote:

> Add some code to ensure that we don't lose communication sync due to
> an oversize message, per suggestion from Oliver Jowett.  I'm a bit
> dubious that this is a real problem, since the client likely doesn't
> have any more space available than the server, but it's not hard to
> make it behave according to the protocol intention.

This can be an issue on clients (like JDBC) that have the ability to
stream data directly to the server.  The client doesn't need to load an
entire file into memory, it can stream it directly from disk to the sever.

Kris Jurka