| 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-04 14:07:53 |
| Message-ID: | CAFj8pRABrydkhnmxr00LDC0w-_4g2JGhYzJ+qRMk4M-mqJ0LbA@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
pá 4. 1. 2019 v 13:58 odesílatel Peter Eisentraut <
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
> 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 | Content-Type | Size |
|---|---|---|
| plpgsql-statement-id-02.patch | text/x-patch | 18.3 KB |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tomas Vondra | 2019-01-04 14:12:05 | Re: Delay locking partitions during query execution |
| Previous Message | Daniel Gustafsson | 2019-01-04 13:45:55 | Re: Allow auto_explain to log to NOTICE |