From: | Greg Smith <gsmith(at)gregsmith(dot)com> |
---|---|
To: | Alan McKay <alan(dot)mckay(at)gmail(dot)com> |
Cc: | Postgres General Postgres General <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: max_allowed_packet equivalent in Postgres? |
Date: | 2009-08-13 19:31:39 |
Message-ID: | alpine.GSO.2.01.0908131518560.19252@westnet.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On Thu, 13 Aug 2009, Alan McKay wrote:
> Make sure your database accepts packages over 5 MB in size. A MySQL
> database for example accepts packages up to 1 MB by default. In this
> case, the value for max_allowed_packet must be increased.
packages->packet for this to make sense; basically they're saying that the
program sends wide rows back and forth to the client, and as described in
http://dev.mysql.com/doc/refman/5.1/en/packet-too-large.html there's a low
default there on that database.
It's possible to run into this general class of issue with PostgreSQL; see
ttp://archives.postgresql.org/pgsql-bugs/2006-07/msg00051.php for one
example.
But that is caused by a problem in the client side application, not the
server. There is no server-side buffer size here as you'll find in MySQL.
If your client app is coded correctly to handle large packets of data, it
should work up to the size limits documented at
http://www.postgresql.org/about/ , so you probably having nothing to worry
about here.
--
* Greg Smith gsmith(at)gregsmith(dot)com http://www.gregsmith.com Baltimore, MD
From | Date | Subject | |
---|---|---|---|
Next Message | Sam Mason | 2009-08-13 22:20:26 | Re: max_allowed_packet equivalent in Postgres? |
Previous Message | Bruce Momjian | 2009-08-13 19:29:47 | Re: max_allowed_packet equivalent in Postgres? |