Pavel Stehule wrote:
> ...
bottleneck is in repeated assign s := s || ..
I will try trick:
create or replace function list(int)
returns varchar as $$
begin
return array_to_string(array(select '' || i || ''
from generate_series(1, $1) g(i)), '');
end$$ language plpgsql immutable;
test
>
> Yep, the more I read, the more I get confused.
> Java loading overhead is a common myth (I can't say if true or false),
> and what Tom writes above can find a tentative place in my mind.
> But still then I can't understand where plsql should or shouldn't be
> used.
>
> I really would enjoy to s
On Jan 22, 2008 2:24 AM, Ivan Sergio Borgonovo <[EMAIL PROTECTED]> wrote:
> > > I doubt that what you were measuring there was either procedure
> > > call overhead or java computational speed; more likely it was the
> > > cost of calling back out of java, through pl/java's JDBC
> > > emulation, dow
On Mon, 21 Jan 2008 21:31:23 -0800
johnf <[EMAIL PROTECTED]> wrote:
> On Monday 21 January 2008 04:47:40 pm Tom Lane wrote:
> > I doubt that what you were measuring there was either procedure
> > call overhead or java computational speed; more likely it was the
> > cost of calling back out of jav
