Re: proposal - plpgsql unique statement id - Mailing list pgsql-hackers

From Pavel Stehule
Subject Re: proposal - plpgsql unique statement id
Date
Msg-id CAFj8pRABrydkhnmxr00LDC0w-_4g2JGhYzJ+qRMk4M-mqJ0LbA@mail.gmail.com
Whole thread Raw
In response to Re: proposal - plpgsql unique statement id  (Peter Eisentraut <peter.eisentraut@2ndquadrant.com>)
Responses Re: proposal - plpgsql unique statement id  (Peter Eisentraut <peter.eisentraut@2ndquadrant.com>)
List pgsql-hackers


pá 4. 1. 2019 v 13:58 odesílatel Peter Eisentraut <peter.eisentraut@2ndquadrant.com> napsal:
On 13/11/2018 14:35, Pavel Stehule wrote:
> I am try to enhance plpgsql_check about profiler functionality and I
> have to solve how to identify every plpgsql statement across different
> sessions. There is lineno, but surely it should not be unique. I propose
> introduce stmtid to every statement structure. This number will be
> unique inside function.

That seems reasonable enough, although I wouldn't use 0 as a valid stmtid.

done


A documenting comment near PLpgSQL_stmt might be nice.

 done

Regards

Pavel


--
Peter Eisentraut              http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
Attachment

pgsql-hackers by date:

Previous
From: Daniel Gustafsson
Date:
Subject: Re: Allow auto_explain to log to NOTICE
Next
From: Tomas Vondra
Date:
Subject: Re: Delay locking partitions during query execution