| From: | Hannu Krosing <hannu(at)tm(dot)ee> |
|---|---|
| To: | Simon Riggs <simon(at)2ndquadrant(dot)com> |
| Cc: | pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: SQL Request Size |
| Date: | 2005-05-16 21:08:37 |
| Message-ID: | 1116277717.4965.3.camel@fuji.krosing.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On E, 2005-05-16 at 21:18 +0100, Simon Riggs wrote:
> What is the maximum SQL statement length that the server will accept?
>
> The libpq message length identifier is 4 bytes, which indicates that the
> max length is 4GB. But thats not exactly the same thing...
>
> Most other systems have a SQL request size limit much smaller than this,
> though I can't find reference to this.
I've had problems with a query generated by slony that was a few hundred
kilobytes in size. It gave me "query too complex" error, probably
overflow somewhere in planner/optimiser.
--
Hannu Krosing <hannu(at)tm(dot)ee>
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2005-05-16 21:16:24 | Re: performance of bitmap scans in nested loop joins |
| Previous Message | Mike Rylander | 2005-05-16 20:20:14 | Re: bitmap scans, btree scans, and tid order |