--=-wHaTULKZ8W1nD4oK4ijD
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
Le samedi 07 octobre 2006 =C3=A0 12:23 -0400, Tom Lane a =C3=A9crit :
Quote:
Martin Pitt <mpitt (AT) debian (DOT) org> writes:
I recently got the Debian bug report below, a server crash with huge
IN clauses.
=20
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.=20 |
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 :
Quote:
Per the documentation:
=20
max_stack_depth (integer)
=20
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.
Quote:
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.
--=20
GNOME http://www.gnomefr.org/
LibGTop http://directory.fsf.org/libgtop.html
--=-wHaTULKZ8W1nD4oK4ijD
Content-Type: application/pgp-signature; name=signature.asc
Content-Description: Ceci est une partie de message
=?ISO-8859-1?Q?num=E9riquement?= =?ISO-8859-1?Q?_sign=E9e?=
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (GNU/Linux)
iD8DBQBFJ+nEliyxJIUSPQoRAkFfAJ9r3wrpSVlM84Z+kFj9ze bBoCk+kACfbV+H
EON9Tcevpdy7MTm4gbg9gko=
=XNyX
-----END PGP SIGNATURE-----
--=-wHaTULKZ8W1nD4oK4ijD--