Re: Fwd: Bug#390730: postgresql-8.1: segfaults on huge
От | Benoît Dejean |
---|---|
Тема | Re: Fwd: Bug#390730: postgresql-8.1: segfaults on huge |
Дата | |
Msg-id | 1160243652.12891.13.camel@localhost.localdomain обсуждение исходный текст |
Ответ на | Re: Fwd: Bug#390730: postgresql-8.1: segfaults on huge litteral IN clauses (Tom Lane <tgl@sss.pgh.pa.us>) |
Список | pgsql-bugs |
Le samedi 07 octobre 2006 à 12:23 -0400, Tom Lane a écrit : > Martin Pitt <mpitt@debian.org> writes: > > I recently got the Debian bug report below, a server crash with huge > > IN clauses. > > What this sounds like to me is someone increasing max_stack_depth > without understanding what he's doing. You must make sure that > max_stack_depth is less than the "ulimit -s" setting the postmaster > is running under ... and not just a little bit less, you want a megabyte > or so of daylight in there. i used ulimit -s 8192 from the start ... and that's my mistake. So you're right, i've misread the documentation, especially that part : > Per the documentation: > > max_stack_depth (integer) > > less a safety margin of a megabyte or so. may be this point should be emphazised in the documentation. Is 1MB of margin really enough ? the doc should be clearer. > So if the OP wants to use huge IN clauses, he has to both increase > max_stack_depth and adjust the ulimit that the postmaster runs under. In order to run my application, i had to raise postgres stack size up to 20MB. I feel like hammering the stack that hard is quite hazardous. But after all, everything works fine :) Thank you for you help. -- GNOME http://www.gnomefr.org/ LibGTop http://directory.fsf.org/libgtop.html
В списке pgsql-bugs по дате отправления: