Re: Reconcile stats in find_tabstat_entry() and get rid of PgStat_BackendFunctionEntry
От | Drouvot, Bertrand |
---|---|
Тема | Re: Reconcile stats in find_tabstat_entry() and get rid of PgStat_BackendFunctionEntry |
Дата | |
Msg-id | f08fee25-1dac-b68b-19af-f4b55ceb3802@gmail.com обсуждение исходный текст |
Ответ на | Re: Reconcile stats in find_tabstat_entry() and get rid of PgStat_BackendFunctionEntry (Andres Freund <andres@anarazel.de>) |
Ответы |
Re: Reconcile stats in find_tabstat_entry() and get rid of PgStat_BackendFunctionEntry
|
Список | pgsql-hackers |
Hi, On 2/16/23 10:21 PM, Andres Freund wrote: > Hi, > > On 2023-02-15 09:21:48 +0100, Drouvot, Bertrand wrote: >> diff --git a/src/backend/utils/activity/pgstat_relation.c b/src/backend/utils/activity/pgstat_relation.c >> index f793ac1516..b26e2a5a7a 100644 >> --- a/src/backend/utils/activity/pgstat_relation.c >> +++ b/src/backend/utils/activity/pgstat_relation.c >> @@ -471,20 +471,46 @@ pgstat_fetch_stat_tabentry_ext(bool shared, Oid reloid) >> * Find any existing PgStat_TableStatus entry for rel_id in the current >> * database. If not found, try finding from shared tables. >> * >> + * If an entry is found, copy it and increment the copy's counters with their >> + * subtransactions counterparts. Then return the copy. There is no need for the >> + * caller to pfree the copy as the MemoryContext will be reset soon after. >> + * > > The "There is no need" bit seems a bit off. Yes, that's true for the current > callers, but who says that it has to stay that way? > Good point. Wording has been changed in V6 attached. > Otherwise this looks ready, on a casual scan. > Thanks for having looked at it! Regards, -- Bertrand Drouvot PostgreSQL Contributors Team RDS Open Source Databases Amazon Web Services: https://aws.amazon.com
Вложения
В списке pgsql-hackers по дате отправления: