> > "Owen Jacobson" <[EMAIL PROTECTED]> writes:
> > > I'd say there's no problem with this, PROVIDED you can ensure
you'll
> > > never abort before completing the computation.
> >
> > Not really an issue in Postgres: we do not support pass-by-reference
> > parameters and are unlikely to start doin
Tom Lane wrote:
> "Owen Jacobson" <[EMAIL PROTECTED]> writes:
> > I'd say there's no problem with this, PROVIDED you can ensure you'll
> > never abort before completing the computation.
>
> Not really an issue in Postgres: we do not support pass-by-reference
> parameters and are unlikely to start
> Daniel Caune wrote:
>> Is there any suggestion against using OUT parameter for local
>> calculation such as using a local variable?
In plpgsql (at least in the current implementation) an OUT parameter is
pretty much just a local variable, and so there's no efficiency argument
against using it as
Daniel Caune wrote:
> Is there any suggestion against using OUT parameter for local
> calculation such as using a local variable?
>
> CREATE OR REPLACE FUNCTION foo(a IN int,
>b1 OUT int,
>b2 OUT int)
> AS $$
> BEGIN
> FOR (...) LO
Hi,
Is there any suggestion against using OUT parameter for local
calculation such as using a local variable?
CREATE OR REPLACE FUNCTION foo(a IN int,
b1 OUT int,
b2 OUT int)
AS $$
BEGIN
FOR (...) LOOP
b1 = (...);
b2 = (...);
