Re: Fix for pg_stat_activity putting client hostaddr into appname field
От | Edmund Horner |
---|---|
Тема | Re: Fix for pg_stat_activity putting client hostaddr into appname field |
Дата | |
Msg-id | CAMyN-kA3Oq6W-pY2Qc3njxKZLJNskp7goD6VRY2rFcO5LhFV7Q@mail.gmail.com обсуждение исходный текст |
Ответ на | Re: Fix for pg_stat_activity putting client hostaddr into appnamefield (Michael Paquier <michael@paquier.xyz>) |
Ответы |
Re: Fix for pg_stat_activity putting client hostaddr into appnamefield
|
Список | pgsql-hackers |
On 29 March 2018 at 20:46, Michael Paquier <michael@paquier.xyz> wrote: > On Tue, Mar 27, 2018 at 03:47:07PM +1300, Edmund Horner wrote: >> But the stats array includes auxiliary processes, which means it has >> NumBackendStatSlots items. The pointers for the aux process strings >> are out of range. In the case of my query, the pointers for >> st_appname in the aux processes happen to point into the >> BackendClientHostnameBuffer segment. >> >> This patch uses NumBackendStatSlots for the sizes of those segments, >> rather than MaxBackends. > > I am adding in CC Robert and Kuntal who worked on that (issue added as > well to the older bug section in v11 open item list). Thanks for making a note of it, Michael. I guess it should be considered for the next patch release of v10 too?
В списке pgsql-hackers по дате отправления: