Re: max_stack_depth problem though query is substantially smaller

Поиск
Список
Период
Сортировка
От Tom Lane
Тема Re: max_stack_depth problem though query is substantially smaller
Дата
Msg-id 7459.1460298542@sss.pgh.pa.us
обсуждение исходный текст
Ответ на max_stack_depth problem though query is substantially smaller  ("Charles Clavadetscher" <clavadetscher@swisspug.org>)
Список pgsql-general
"Bannert  Matthias" <bannert@kof.ethz.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
haveunderstand 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


В списке pgsql-general по дате отправления:

Предыдущее
От: "durumdara@gmail.com"
Дата:
Сообщение: Re: Really unique session ID - PID + connection timestamp?
Следующее
От: Michael Nolan
Дата:
Сообщение: Re: Bypassing NULL elements in row_to_json function