| From: | Jeff Davis <pgsql(at)j-davis(dot)com> |
|---|---|
| To: | Josh Berkus <josh(at)agliodbs(dot)com> |
| Cc: | Neil Conway <nrc(at)cs(dot)berkeley(dot)edu>, Steve Atkins <steve(at)blighty(dot)com>, SF PostgreSQL <sfpug(at)postgresql(dot)org> |
| Subject: | Re: IN question |
| Date: | 2008-12-11 18:21:21 |
| Message-ID: | 1229019681.15122.5.camel@dell.linuxdev.us.dell.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | sfpug |
On Thu, 2008-12-11 at 10:05 -0800, Josh Berkus wrote:
> Yes. For example, if the length of your query exceeds any of various
> memory limits on Linux, the connection crashes with a very unfriendly
> error message. If it was our limit, the error message could at least be
> friendly: "Query string too long. Please edit the query or increase
> work_mem."
>
In Linux, the consequences are actually much worse: usually it would
kill the _postmaster_:
http://lkml.indiana.edu/hypermail/linux/kernel/0702.1/0616.html
I'm not suggesting we add features to work around this kind of
insanity, but it's at least one example of an error that we could
handle more gracefully than the OS can.
Regards,
Jeff Davis
| From | Date | Subject | |
|---|---|---|---|
| Next Message | A. Elein Mustain | 2008-12-14 00:45:34 | Re: IN question |
| Previous Message | Josh Berkus | 2008-12-11 18:05:35 | Re: IN question |