Re: [PATCH] Refactoring of LWLock tranches - Mailing list pgsql-hackers

From Andres Freund
Subject Re: [PATCH] Refactoring of LWLock tranches
Date
Msg-id 17891D36-9277-4138-927B-FF21531FF19F@anarazel.de
Whole thread Raw
In response to Re: [PATCH] Refactoring of LWLock tranches  (Robert Haas <robertmhaas@gmail.com>)
Responses Re: [PATCH] Refactoring of LWLock tranches  (Robert Haas <robertmhaas@gmail.com>)
List pgsql-hackers
On November 19, 2015 8:09:38 AM PST, Robert Haas <robertmhaas@gmail.com> wrote:
>On Thu, Nov 19, 2015 at 9:04 AM, Ildus Kurbangaliev
><i.kurbangaliev@postgrespro.ru> wrote:
>> The moving base tranches to shared memory has been discussed many
>times.
>> The point is using them later in pg_stat_activity and other
>monitoring
>> views.
>
>I'm not in agreement with this idea.  Actually, I'd prefer that the
>tranches live in backend-private memory, not shared memory, so that we
>could for example add backend-local counters to them if desired.  

I don't buy that argument. It'd be nearly trivial to have a backend_tranchestats array, indexed by the tranche id, for
suchcounters.
 

It's really not particularly convenient to allocate tranches right now. You have to store at least the identifier in
sharedmemory and then redo the registration in each process. Otherwise some processes can't identify them. Which of
ratherinconvenient of you want to register some at runtime
 


--- 
Please excuse brevity and formatting - I am writing this on my mobile phone.



pgsql-hackers by date:

Previous
From: Nikolay Shaplov
Date:
Subject: Re: [PROPOSAL] TAP test example
Next
From: Tom Lane
Date:
Subject: Re: proposal: LISTEN *