Re: proposal - plpgsql unique statement id
От | Peter Eisentraut |
---|---|
Тема | Re: proposal - plpgsql unique statement id |
Дата | |
Msg-id | a18215fd-c50a-6a23-a737-183385f31a01@2ndquadrant.com обсуждение исходный текст |
Ответ на | Re: proposal - plpgsql unique statement id (Pavel Stehule <pavel.stehule@gmail.com>) |
Ответы |
Re: proposal - plpgsql unique statement id
|
Список | pgsql-hackers |
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? -- Peter Eisentraut http://www.2ndQuadrant.com/ PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
В списке pgsql-hackers по дате отправления: