Re: concat_ws

From: "Mendola Gaetano" <mendola(at)bigfoot(dot)com>
To: <pgsql-admin(at)postgresql(dot)org>
Cc: "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Subject: Re: concat_ws
Date: 2003-08-03 23:20:21
Message-ID: 005b01c35a15$cfbd7960$10d4a8c0@mm.eutelsat.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-admin pgsql-hackers

"Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> Joe Conway <mail(at)joeconway(dot)com> writes:
> > Tom Lane wrote:
> >> It seems to be running out of memory.
>
> > Also worth noting, without STRICT, even a plain EXPLAIN *without*
> > ANALYZE causes the problem to show itself.
>
> Yeah. The problem is that the SQL function inliner generates an
> enormous expression tree from this function definition. 7.3 had no
> inliner so no problem.
>
> I am not sure what to do about it --- the only idea that comes to mind
> is to put an arbitrary limit (of, say, 5 or 10 function calls) on the
> depth of inlining expansion. That seems like a pretty ugly answer
> ... anyone have a better one?

Please no one tell to add another ugly parameter on postgresql.conf

My cent.

Regards
Gaetano Mendola

In response to

Browse pgsql-admin by date

  From Date Subject
Next Message Tom Lane 2003-08-03 23:27:13 Re: [HACKERS] concat_ws
Previous Message Joe Conway 2003-08-03 23:16:11 Re: [HACKERS] concat_ws

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2003-08-03 23:27:13 Re: [HACKERS] concat_ws
Previous Message Joe Conway 2003-08-03 23:16:11 Re: [HACKERS] concat_ws