Re: [UPDATED] A GUC variable to replace PGBE_ACTIVITY_SIZE
От
Tom Lane
Тема
Re: [UPDATED] A GUC variable to replace PGBE_ACTIVITY_SIZE
Дата
Msg-id
2982.1214920573@sss.pgh.pa.us
Ответ на
Re: [UPDATED] A GUC variable to replace PGBE_ACTIVITY_SIZE (Heikki Linnakangas)
Список
Дерево обсуждения
A GUC variable to replace PGBE_ACTIVITY_SIZE Thomas Lee <tom@vector-seven.com>
Re: A GUC variable to replace PGBE_ACTIVITY_SIZE Neil Conway <neilc@samurai.com>
Re: A GUC variable to replace PGBE_ACTIVITY_SIZE "Heikki Linnakangas" <heikki@enterprisedb.com>
Re: [UPDATED] A GUC variable to replace PGBE_ACTIVITY_SIZE Thomas Lee <tom@vector-seven.com>
Re: [UPDATED] A GUC variable to replace PGBE_ACTIVITY_SIZE "Heikki Linnakangas" <heikki@enterprisedb.com>
Re: [UPDATED] A GUC variable to replace PGBE_ACTIVITY_SIZE Tom Lane <tgl@sss.pgh.pa.us>
Re: [UPDATED] A GUC variable to replace PGBE_ACTIVITY_SIZE "Heikki Linnakangas" <heikki@enterprisedb.com>
Re: [UPDATED] A GUC variable to replace PGBE_ACTIVITY_SIZE Tom Lane <tgl@sss.pgh.pa.us>
"Heikki Linnakangas" writes: > Tom Lane wrote: >> Huh? How could we be assigning to a slot that is not in use? > Before the patch, we loop through the shared PgBackendStatus slots > (there is MaxBackends of them), and issue a memcpy for each to copy it > to our local slot. After that, we check if it was actually in use. > After the patch, we still loop through the shared slots, but only issue > the memcpy for slots that are in use. Oh, you're talking about *fetching* the slot contents, not *assigning* to them. Sorry, probably should have read the patch instead of just reacting to the comment ... regards, tom lane
В списке pgsql-patches по дате отправления
От: Heikki Linnakangas
Дата: