On 10/6/06, Jean Tourrilhes <[EMAIL PROTECTED]> wrote:
The following bug has been logged online:
Bug reference: 2681
Logged by: Jean Tourrilhes
Email address: [EMAIL PROTECTED]
PostgreSQL version: 7.4.7
Operating system: Linux - Debian 3.1 (stable)
Description:dupli
Le samedi 07 octobre 2006 à 12:23 -0400, Tom Lane a écrit :
> Martin Pitt <[EMAIL PROTECTED]> 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 doi
The following bug has been logged online:
Bug reference: 2681
Logged by: Jean Tourrilhes
Email address: [EMAIL PROTECTED]
PostgreSQL version: 7.4.7
Operating system: Linux - Debian 3.1 (stable)
Description:duplicate key violates unique constraint
Details:
Hi,
Martin Pitt <[EMAIL PROTECTED]> 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
Hi PostgreSQL developers,
I recently got the Debian bug report below, a server crash with huge
IN clauses.
Benoît did not give a concrete example of how to actually cause the
crash, just the recipe. I was able to reproduce the crash with
echo "select count(*) from foo where id in (`seq -s ','