Re: show fct_name of the function/procedure

On Saturday, April 27, 2024, ft wrote: > > fct_name text := pg_fct_name(); -- I need it > > https://www.postgresql.org/docs/current/plpgsql-statements.html#PLPGSQL-STATEMENTS-DIAGNOSTICS PG_ROUTINE_OID I think casting that to “regproc” will get you what you need. Otherwise there should

show fct_name of the function/procedure

Hello, I need (a very simple construct) to show the fct_name/proc_name  for the function/procedure. Example: create procedure/function bet_process() as $$ declare pid int := pg_backend_pid() ; -- it works fine fct_name text := pg_fct_name(); -- I need it begin -- do s.th like -

Re: Stess test via libpq for postgreSQL DB

Thanks David Regards, Sasmit Utkarsh +91-7674022625 On Sat, Apr 27, 2024 at 11:44 PM David G. Johnston < david.g.johns...@gmail.com> wrote: > On Sat, Apr 27, 2024 at 11:07 AM Sasmit Utkarsh > wrote: > >> >> But i have some clarifications if we can use it to execute PLSQL code >> blocks rather

Re: Stess test via libpq for postgreSQL DB

On Sat, Apr 27, 2024 at 11:07 AM Sasmit Utkarsh wrote: > > But i have some clarifications if we can use it to execute PLSQL code > blocks rather than standalone SQL queries. > https://www.postgresql.org/docs/current/sql-do.html David J.

Stess test via libpq for postgreSQL DB

Hi Postgresql Team, Could you please help on how to get started with some stress test for my application which uses libpq to interact with postgres flexi db. I tried to explore pgbench which is a builtin tool to get some stats. But i have some clarifications if we can use it to execute PLSQL code

Re: Monitoring and debugging historical performance

Hi, On Sat, Apr 27, 2024 at 10:01 PM sud wrote: > > Hi All, > While looking option to see how one can monitor database performance for > debugging into historical database performance issues (historical database > wait events , CPU/memory utilization in past, query execution times in past , >

Monitoring and debugging historical performance

Hi All, While looking option to see how one can monitor database performance for debugging into historical database performance issues (historical database wait events , CPU/memory utilization in past, query execution times in past , executions paths at any point in time in past etc), It appears th

RE: Performance degradation after upgrading from 9.5 to 14

På lørdag 27. april 2024 kl. 11:46:26, skrev Zahir Lalani < ZahirLalani@oliver.agency >: Same issue and took us ages to work out that is was JIT! The default is on, and setting off solves the problem. I have seen several blogs reporting the same and so wonder

RE: Performance degradation after upgrading from 9.5 to 14

Same issue and took us ages to work out that is was JIT! The default is on, and setting off solves the problem. I have seen several blogs reporting the same and so wonder why this default is on? Z From: Олександр Янін Sent: Monday, April 22, 2024 8:01 PM To: Johnathan Tiamoh Cc: pgsql-general