From: | "Gurjeet Singh" <singh(dot)gurjeet(at)gmail(dot)com> |
---|---|
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:33:28 |
Message-ID: | 65937bea0611020833h373e0300gcaa525fd7bb17060@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
But I do not understand why the IN list has to make so many recursive
calls???
I know if it was possible, it'd have been done already... but can 'making it
iterative' (whatever 'it' stands for) be reconsidered?
--
gurjeet[(dot)singh](at)EnterpriseDB(dot)com
singh(dot)gurjeet(at){ gmail | hotmail | yahoo }.com
On 11/2/06, Alvaro Herrera <alvherre(at)commandprompt(dot)com> wrote:
>
> I notice it crashes with max_stack_depth set to 8173, but correctly
> detects the error with max_stack_depth set to 8172. The doc suggests a
> safety margin of "a megabyte or so", so I think we are conforming to our
> docs here.
>
> Tom recently added a check for getrlimit(RLIMIT_STACK), but I don't know
> if that considered the "megabyte or so". *peeks the code* Yeah,
> there's a 512 kb "daylight", but there's also an absolute maximum of
> 2MB.
>
From | Date | Subject | |
---|---|---|---|
Next Message | Benjamin Weaver | 2006-11-02 16:36:49 | explosion of tiny tables representing multiple fields--Is this necessary? |
Previous Message | Tom Lane | 2006-11-02 16:27:23 | Re: DELETE performance issues |