Re: pgsql: Add some code to ensure that we don't lose

From: Kris Jurka <books(at)ejurka(dot)com>
To: Tom Lane <tgl(at)svr1(dot)postgresql(dot)org>
Cc: pgsql-committers(at)postgresql(dot)org
Subject: Re: pgsql: Add some code to ensure that we don't lose
Date: 2004-10-19 01:15:08
Message-ID: Pine.BSO.4.56.0410182013030.11510@leary.csoft.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-committers

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

In response to

Browse pgsql-committers by date

  From Date Subject
Next Message Peter Eisentraut 2004-10-19 13:38:54 pgsql: Organize the help output a little better.
Previous Message Tom Lane 2004-10-18 23:23:29 pgsql: Add some code to ensure that we don't lose communication sync due