From: | Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com> |
---|---|
To: | Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com> |
Cc: | PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: proposal - plpgsql unique statement id |
Date: | 2019-01-18 10:11:24 |
Message-ID: | CAFj8pRDCoWgQFw3+DBZ=V89xY9mvqT9pAak_S04ZK-ZSHEnb1w@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
pá 18. 1. 2019 v 8:56 odesílatel Peter Eisentraut <
peter(dot)eisentraut(at)2ndquadrant(dot)com> napsal:
> On 04/01/2019 15:07, Pavel Stehule wrote:
> > pá 4. 1. 2019 v 13:58 odesílatel Peter Eisentraut
> > <peter(dot)eisentraut(at)2ndquadrant(dot)com
> > <mailto:peter(dot)eisentraut(at)2ndquadrant(dot)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 | Content-Type | Size |
---|---|---|
plpgsql-statement-id-03.patch | text/x-patch | 18.5 KB |
From | Date | Subject | |
---|---|---|---|
Next Message | Amit Khandekar | 2019-01-18 10:21:28 | Re: Pluggable Storage - Andres's take |
Previous Message | Andrew Gierth | 2019-01-18 10:05:53 | Re: Ryu floating point output patch |