| From: | Alvaro Herrera <alvherre(at)commandprompt(dot)com> |
|---|---|
| To: | Markus Schiltknecht <markus(at)bluegap(dot)ch> |
| Cc: | pgsql general <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: lots of values for IN() clause |
| Date: | 2006-11-02 16:01:20 |
| Message-ID: | 20061102160120.GF25444@alvh.no-ip.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
Markus Schiltknecht wrote:
> Hi,
>
> One of our PostgreSQL 8.1.5 databases constantly crashed on a certain
> query (backend SEGFAULTs). I've figured the crashes were caused by a
> very long IN() clause.
>
> You can easily reproduce the crash by feeding the output of the python
> script below to your database.
I'd argue that you have max_stack_depth set to an invalid value (higher
than your true stack limit). I tried your example here on 8.1.5 and got
this:
alvherre=# \i foo
CREATE TABLE
psql:foo:2: ERROR: stack depth limit exceeded
HINT: Increase the configuration parameter "max_stack_depth".
DROP TABLE
--
Alvaro Herrera http://www.CommandPrompt.com/
The PostgreSQL Company - Command Prompt, Inc.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Alvaro Herrera | 2006-11-02 16:02:55 | Re: lots of values for IN() clause |
| Previous Message | Shelby Cain | 2006-11-02 16:00:19 | Re: lots of values for IN() clause |