Re: [ADMIN] concat_ws - Mailing list pgsql-hackers

From Dennis Björklund
Subject Re: [ADMIN] concat_ws
Date
Msg-id Pine.LNX.4.44.0308040737460.26410-100000@zigo.dhs.org
Whole thread Raw
In response to Re: [ADMIN] concat_ws  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: [ADMIN] concat_ws  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
On Sun, 3 Aug 2003, Tom Lane wrote:

> I added code to inline_function to stop inlining if a parameter
> expression to be substituted multiple times has cost greater than
> 10*cpu_operator_cost (which roughly means that it contains more than
> 10 operators or functions).

When is this inlining taking place and what is the logic? I just want to
make sure that there is no code in pg that will unfold forever, say for
example for a recursive fac() function. From the above it sounds like that
might be a problem.

--
/Dennis


pgsql-hackers by date:

Previous
From: Oleg Bartunov
Date:
Subject: Re: Release changes
Next
From: "Christopher Kings-Lynne"
Date:
Subject: Re: Release changes