From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Panagiotis Papadakos <papadako(at)csd(dot)uoc(dot)gr> |
Cc: | pgsql-jdbc(at)postgresql(dot)org |
Subject: | Re: Problem with very big queries. |
Date: | 2008-04-10 23:20:51 |
Message-ID: | 25452.1207869651@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-jdbc |
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.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2008-04-10 23:22:30 | Re: Problem with very big queries. |
Previous Message | Panagiotis Papadakos | 2008-04-10 23:10:37 | Re: Problem with very big queries. |