From: | Martijn van Oosterhout <kleptog(at)svana(dot)org> |
---|---|
To: | Bill Thoen <bthoen(at)gisnet(dot)com> |
Cc: | Andrej Ricnik-Bay <andrej(dot)groups(at)gmail(dot)com>, pgsql-general(at)postgresql(dot)org |
Subject: | Re: PG Seg Faults Performing a Query |
Date: | 2007-08-22 13:33:02 |
Message-ID: | 20070822133302.GA16592@svana.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general pgsql-hackers |
On Wed, Aug 22, 2007 at 07:09:22AM -0600, Bill Thoen wrote:
> PostgreSQL Version is 8.1.5, running on Linux (Fedora Core 6). The last few
> lines in the Serverlog are:
> LOG: unexpected EOF on client connection
> LOG: transaction ID wrap limit is 1073746500, limited by database
> "postgres"
> LOG: transaction ID wrap limit is 1073746500, limited by database
> "postgres"
All indications are that your client is unable to hold the 18 million
row result and crashing with out of memory. Nothing you do in the
server or client is going to magic more memory for you, you need to
avoid getting it in the first place.
If you only want to display part of it, do a LIMIT <rows>. Or use a
cursor to page through it.
That said, it would be nice if it returned an error instead of
crashing.
Have a nice day,
--
Martijn van Oosterhout <kleptog(at)svana(dot)org> http://svana.org/kleptog/
> From each according to his ability. To each according to his ability to litigate.
From | Date | Subject | |
---|---|---|---|
Next Message | Alvaro Herrera | 2007-08-22 13:42:18 | Re: PG Seg Faults Performing a Query |
Previous Message | Bill Thoen | 2007-08-22 13:09:22 | Re: PG Seg Faults Performing a Query |
From | Date | Subject | |
---|---|---|---|
Next Message | Alvaro Herrera | 2007-08-22 13:42:18 | Re: PG Seg Faults Performing a Query |
Previous Message | Hamid Quddus Akhtar | 2007-08-22 13:21:20 | Re: Crash with empty dictionary |