Skip site navigation (1) Skip section navigation (2)

Re: Problem with very big queries.

From: Panagiotis Papadakos <papadako(at)csd(dot)uoc(dot)gr>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: pgsql-jdbc(at)postgresql(dot)org
Subject: Re: Problem with very big queries.
Date: 2008-04-10 23:29:49
Message-ID: 200804110229.49368.papadako@csd.uoc.gr (view raw or flat)
Thread:
Lists: pgsql-jdbc
On Friday 11 April 2008 02:20:51 Tom Lane wrote:
> Panagiotis Papadakos <papadako(at)csd(dot)uoc(dot)gr> writes:
> > I want to send to postgresql-8.0 a very big query,
> > select * from table where lala IN (....)
> > Inside IN there are almost 60000 values.
> >
> > Unfortunately, the server terminates with a singal 11 and I get
> > to my console the following:
>
> It shouldn't crash.  I suspect you tried this, got
>
> ERROR:  stack depth limit exceeded
> HINT:  Increase the configuration parameter "max_stack_depth".
>
> and blindly followed the HINT without any regard for whether the value
> you picked was actually safe on your platform.  If you make
> max_stack_depth bigger than what the kernel allows, you will indeed
> get a crash; but that's not a bug it's pilot error.
>
> More recent PG versions try to limit max_stack_depth to a safe value,
> but 8.0 just believes what you tell it.
Yep you are correct. But I have set the value to 8192, based on ulimit -s but 
it still crashes.
>
> 			regards, tom lane



In response to

pgsql-jdbc by date

Next:From: John R PierceDate: 2008-04-10 23:52:15
Subject: Re: Problem with very big queries.
Previous:From: Panagiotis PapadakosDate: 2008-04-10 23:27:33
Subject: Re: Problem with very big queries.

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group