From: | Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org> |
---|---|
To: | Markus Schiltknecht <markus(at)bluegap(dot)ch>, pgsql general <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: lots of values for IN() clause |
Date: | 2006-11-02 16:02:55 |
Message-ID: | 20061102160255.GG25444@alvh.no-ip.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Alvaro Herrera wrote:
> 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:
Forgot to quote the value:
alvherre=# show max_stack_depth ;
max_stack_depth
-----------------
2048
(1 fila)
This is a stock ix86 machine running Linux 2.6.
--
Alvaro Herrera http://www.flickr.com/photos/alvherre/
"Ellos andaban todos desnudos como su madre los parió, y también las mujeres,
aunque no vi más que una, harto moza, y todos los que yo vi eran todos
mancebos, que ninguno vi de edad de más de XXX años" (Cristóbal Colón)
From | Date | Subject | |
---|---|---|---|
Next Message | Richard Huxton | 2006-11-02 16:03:22 | Re: lots of values for IN() clause |
Previous Message | Alvaro Herrera | 2006-11-02 16:01:20 | Re: lots of values for IN() clause |