| From: | Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com> |
|---|---|
| To: | Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: proposal - plpgsql unique statement id |
| Date: | 2019-01-04 12:58:00 |
| Message-ID: | 5cdd1c59-42e1-be1e-ad5f-9620c4566e93@2ndquadrant.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
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.
A documenting comment near PLpgSQL_stmt might be nice.
--
Peter Eisentraut http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Michael Paquier | 2019-01-04 13:00:48 | Re: BUG #15548: Unaccent does not remove combining diacritical characters |
| Previous Message | Michael Paquier | 2019-01-04 12:52:52 | Re: don't create storage when unnecessary |