>In your example, the bottleneck is calling the function f1. So you need to
>check only this function. It is not important if other functions or
>>procedures do database lookups.
>Or if it does just one database lookup, then you can use SQL language. I
>repeat, PL/pgSQL is not good for ultra ve
pá 30. 7. 2021 v 10:12 odesílatel Daniel Westermann (DWE) <
daniel.westerm...@dbi-services.com> napsal:
>
> pá 30. 7. 2021 v 9:12 odesílatel Daniel Westermann (DWE) <
> daniel.westerm...@dbi-services.com> napsal:
>
> Hi,
>
> we have a customer which was migrated from Oracle to PostgreSQL 12.5 (I
>
pá 30. 7. 2021 v 9:12 odesílatel Daniel Westermann (DWE)
mailto:daniel.westerm...@dbi-services.com>>
napsal:
Hi,
we have a customer which was migrated from Oracle to PostgreSQL 12.5 (I know,
the latest version is 12.7). The migration included a lot of PL/SQL code.
Attached a very simplified t
pá 30. 7. 2021 v 10:04 odesílatel Pavel Stehule
napsal:
> Hi
>
> pá 30. 7. 2021 v 10:02 odesílatel Imre Samu napsal:
>
>> Hi Daniel,
>>
>> side note:
>>
>> Maybe you can tune the "function" with some special query optimizer
>> attributes:
>> IMMUTABLE | STABLE | VOLATILE | PARALLEL SAFE
>>
Hi
pá 30. 7. 2021 v 9:12 odesílatel Daniel Westermann (DWE) <
daniel.westerm...@dbi-services.com> napsal:
> Hi,
>
> we have a customer which was migrated from Oracle to PostgreSQL 12.5 (I
> know, the latest version is 12.7). The migration included a lot of PL/SQL
> code. Attached a very simplifie
Hi
pá 30. 7. 2021 v 10:02 odesílatel Imre Samu napsal:
> Hi Daniel,
>
> side note:
>
> Maybe you can tune the "function" with some special query optimizer
> attributes:
> IMMUTABLE | STABLE | VOLATILE | PARALLEL SAFE
>
> so in your example:
> create or replace function f1(int) returns
Hi Daniel,
side note:
Maybe you can tune the "function" with some special query optimizer
attributes:
IMMUTABLE | STABLE | VOLATILE | PARALLEL SAFE
so in your example:
create or replace function f1(int) returns double precision as
$$
declare
begin
return 1;
end;
$$ language plpgsql
Hi,
we have a customer which was migrated from Oracle to PostgreSQL 12.5 (I know,
the latest version is 12.7). The migration included a lot of PL/SQL code.
Attached a very simplified test case. As you can see there are thousands, even
nested calls to procedures and functions. The test case does
