Re: max_stack_depth problem though query is substantially smaller

"Bannert Matthias" <bannert(at)kof(dot)ethz(dot)ch> writes:
> Fwiw, I was not stubbornly insisting on nesting operators. Actually I switched from "=>" to the hstore function cause
> a note in the manual said it was deprecated (http://www.postgresql.org/docs/9.0/static/hstore.html) Somehow I must have understand that note the wrong way.
> What's your take on that operator being deprecated?

That's the old SQL operator (which is not even there anymore) that's
equivalent to the hstore(text,text) constructor function, ie
"text => text returning hstore". It's quite a different concept
from the => notation inside an hstore literal. That is:
'foo'::text => 'bar'::text
is not like
'"foo" => "bar"'::hstore
even though they have the same end result.

regards, tom lane