Postgres Pro
Downloads
Home   >   mailing lists

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

From Pavel Stehule
Subject Re: proposal - plpgsql unique statement id
Date
Msg-id CAFj8pRDCoWgQFw3+DBZ=V89xY9mvqT9pAak_S04ZK-ZSHEnb1w@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
Tree view


pá 18. 1. 2019 v 8:56 odesílatel Peter Eisentraut <peter.eisentraut@2ndquadrant.com> napsal:
On 04/01/2019 15:07, Pavel Stehule wrote:
> pá 4. 1. 2019 v 13:58 odesílatel Peter Eisentraut
> <peter.eisentraut@2ndquadrant.com
> <mailto: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

Related, should stmtid be unsigned int rather than signed int?

done

Regards

Pavel

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

pgsql-hackers by date:

Previous
From: Andrew Gierth
Date:
Subject: Re: Ryu floating point output patch
Next
From: Amit Khandekar
Date:
Subject: Re: Pluggable Storage - Andres's take