| From: | "Daniel Westermann (DWE)" <daniel(dot)westermann(at)dbi-services(dot)com> |
|---|---|
| To: | Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com> |
| Cc: | "pgsql-performance(at)lists(dot)postgresql(dot)org" <pgsql-performance(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: Performance issue with thousands of calls to procedures and functions? |
| Date: | 2021-07-30 11:15:19 |
| Message-ID: | ZR0P278MB09209FF50B53E76B48CF3E2BD2EC9@ZR0P278MB0920.CHEP278.PROD.OUTLOOK.COM |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-performance |
>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 very frequent calls (where >there is minimal other overhead).
>Generally, start of function or start of query are more expensive on Postgres than on Oracle. Postgres is much more dynamic, and it needs >to do some rechecks. The overhead is in nanoseconds, but nanoseconds x billions are lot of seconds
Thank you Pavel, for all the information. That was very helpful.
Regards
Daniel
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Nikhil Shetty | 2021-08-04 15:06:46 | Logical Replication speed-up initial data |
| Previous Message | Pavel Stehule | 2021-07-30 08:21:53 | Re: Performance issue with thousands of calls to procedures and functions? |