From: Tom Lane <tgl@sss.pgh.pa.us>
To: terry <94487509@qq.com>
Cc: pgsql-performance@postgresql.org <pgsql-performance@postgresql.org>
Subject: Re: can we optimize STACK_DEPTH_SLOP
Date: Sat, 20 Feb 2010 22:25:03 -0500
Message-ID: <28110.1266722703@sss.pgh.pa.us> (raw)
In-Reply-To: <tencent_7683C70774EC20361E8F1D79@qq.com>
References: <tencent_7683C70774EC20361E8F1D79@qq.com>
"=?ISO-8859-1?B?dGVycnk=?=" <94487509@qq.com> writes:
> STACK_DEPTH_SLOP stands for Required daylight between max_stack_depth and the kernel limit, in bytes.
> Why we need so much memory? MySql need only no more than 100K. Where these memory allocated for?
That's not memory, that's just address space. Cutting it will not
really buy you anything; it'll just increase your risk of stack-overflow
crashes.
regards, tom lane
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-performance@postgresql.org
Cc: tgl@sss.pgh.pa.us, 94487509@qq.com
Subject: Re: can we optimize STACK_DEPTH_SLOP
In-Reply-To: <28110.1266722703@sss.pgh.pa.us>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox