| From: | "Heikki Linnakangas" <heikki(at)enterprisedb(dot)com> |
|---|---|
| To: | "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | "PostgreSQL-development" <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Default of max_stack_depth and getrlimit |
| Date: | 2008-07-21 15:23:39 |
| Message-ID: | 4884A9FB.7000505@enterprisedb.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Tom Lane wrote:
> "Heikki Linnakangas" <heikki(at)enterprisedb(dot)com> writes:
>> In 8.2, we started to use getrlimit(RLIMIT_STACK, ...) to set
>> max_stack_depth automatically, to a max of 2MB:
>
>> http://archives.postgresql.org/pgsql-hackers/2006-10/msg00389.php
>
>> However, it's not behaving as I expected when the stack limit is set to
>> "unlimited".
>
> Is there really any such thing as "unlimited" stack depth?
No, but I would think it's safe to assume that "unlimited" is greater
than 2MB.
--
Heikki Linnakangas
EnterpriseDB http://www.enterprisedb.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2008-07-21 15:27:14 | Re: Re: [COMMITTERS] pgsql: Adjust things so that the query_string of a cached plan and the |
| Previous Message | Andrew Dunstan | 2008-07-21 15:19:40 | Re: pg_dump additional options for performance |