Re: [UPDATED] A GUC variable to replace PGBE_ACTIVITY_SIZE - Mailing list pgsql-patches

From Tom Lane
Subject Re: [UPDATED] A GUC variable to replace PGBE_ACTIVITY_SIZE
Date
Msg-id 2982.1214920573@sss.pgh.pa.us
Whole thread Raw
In response to Re: [UPDATED] A GUC variable to replace PGBE_ACTIVITY_SIZE  ("Heikki Linnakangas" <heikki@enterprisedb.com>)
List pgsql-patches
"Heikki Linnakangas" <heikki@enterprisedb.com> 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 by date:

Previous
From: "Heikki Linnakangas"
Date:
Subject: Re: [UPDATED] A GUC variable to replace PGBE_ACTIVITY_SIZE
Next
From: Bruce Momjian
Date:
Subject: Re: [HACKERS] odd output in restore mode