Postgres Pro
Downloads
Home   >   mailing lists

Thread: how to trace a backend session

how to trace a backend session

From
James Pang
Date:
experts,
    We migrated our database from Oracle to Postgresql recently, we used to turn on Oracle session trace(that will capture all activities, SQL statements, waiting, waiting time), to do living troubleshooting.  could you direct any similar tracing in Postgresql v13 , v14. 

Thanks,

James 

Re: how to trace a backend session

From
Pierre Forstmann
Date:
Hello,

I have coded an extension to trace SQL statements for specific backends: https://github.com/pierreforstmann/pg_log_statements
(only SQL statements are traced - no wait events data is collected).

Pierre

Le lun. 22 janv. 2024 à 08:29, James Pang <jamespang886@gmail.com> a écrit :
experts,
    We migrated our database from Oracle to Postgresql recently, we used to turn on Oracle session trace(that will capture all activities, SQL statements, waiting, waiting time), to do living troubleshooting.  could you direct any similar tracing in Postgresql v13 , v14. 

Thanks,

James 

Re: how to trace a backend session

From
Dominique Devienne
Date:
Le lun. 22 janv. 2024 à 08:29, James Pang <jamespang886@gmail.com> a écrit :
[...] we used to turn on Oracle session trace(that will capture all activities,
SQL statements, waiting, waiting time), to do living troubleshooting.
could you direct any similar tracing in Postgresql v13 , v14. 

On Tue, Jan 23, 2024 at 7:45 PM Pierre Forstmann <pierre.forstmann@gmail.com> wrote:
I have coded an extension to trace SQL statements for specific backends: https://github.com/pierreforstmann/pg_log_statements
(only SQL statements are traced - no wait events data is collected).

There's also the possibility of activating client-side tracing with libpq, if you are using it:

Not the same thing as server-side tracing, of course. But can be useful. --DD

PS: Although that trace is not easily machine parse'able, it is at least human readable (kinda...)