From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Lincoln Yeoh <lyeoh(at)pop(dot)jaring(dot)my> |
Cc: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: Max query limit in 7.1? With TOAST? |
Date: | 2001-02-15 15:12:10 |
Message-ID: | 2265.982249930@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Lincoln Yeoh <lyeoh(at)pop(dot)jaring(dot)my> writes:
> What is the max query size for 7.1?
There's no specific upper limit, and has not been since 7.0.
The reason mysql's crashme test crashes when run against recent Postgres
releases is that it tries to determine the max query string length by
experiment. Unfortunately, the Perl code they use to do this is more
of a memory hog than the backend itself, and so the Perl process runs
out of memory first. I have MAXDSIZ set to 128Mb, and I see the Perl
process die with a malloc() failure when the backend is still well under
100Mb. Not sure what query string length it's testing at that point,
but presumably on the order of ten meg...
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2001-02-15 15:15:27 | Re: TPCH questions |
Previous Message | Richard Huxton | 2001-02-15 15:09:16 | Re: last UPDATE or INSERT time of a table? |