Re: RFC: replace pg_stat_activity.waiting with something more descriptive

From: Ildus Kurbangaliev <i(dot)kurbangaliev(at)postgrespro(dot)ru>
To: Andres Freund <andres(at)anarazel(dot)de>
Cc: Pg Hackers <pgsql-hackers(at)postgresql(dot)org>, Robert Haas <robertmhaas(at)gmail(dot)com>, Alexander Korotkov <aekorotkov(at)gmail(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Amit Kapila <amit(dot)kapila16(at)gmail(dot)com>
Subject: Re: RFC: replace pg_stat_activity.waiting with something more descriptive
Date: 2015-07-21 11:28:25
Message-ID: 55AE2CD9.4050005@postgrespro.ru
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 07/21/2015 01:18 PM, Andres Freund wrote:
> On 2015-07-21 13:11:36 +0300, Ildus Kurbangaliev wrote:
>>
>> /*
>> * Top-level transactions are identified by VirtualTransactionIDs comprising
>> diff --git a/src/include/storage/lwlock.h b/src/include/storage/lwlock.h
>> index cff3b99..55b0687 100644
>> --- a/src/include/storage/lwlock.h
>> +++ b/src/include/storage/lwlock.h
>> @@ -58,6 +58,9 @@ typedef struct LWLock
>> #ifdef LOCK_DEBUG
>> struct PGPROC *owner; /* last exlusive owner of the lock */
>> #endif
>> +
>> + /* LWLock group, initialized as -1, calculated in first acquire */
>> + int group;
>> } LWLock;
> I'd very much like to avoid increasing the size of struct LWLock. We
> have a lot of those and I'd still like to inline them with the buffer
> descriptors. Why do we need a separate group and can't reuse the
> tranche? That might require creating a few more tranches, but ...?
>
> Andres
Do you mean moving LWLocks defined by offsets and with dynamic sizes to
separate tranches?
It sounds like an good option, but it will require refactoring of
current tranches. In current implementation
i tried not change current things.

Simple solution will be using uint8 for tranche (because we have only 3
of them now,
and it will take much time to get to 255) and uint8 for group. In this
case size will not change.

--
Ildus Kurbangaliev
Postgres Professional: http://www.postgrespro.com
The Russian Postgres Company

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Alvaro Herrera 2015-07-21 11:38:39 Re: [BUGS] object_classes array is broken, again
Previous Message Alexander Korotkov 2015-07-21 11:00:31 Re: Fillfactor for GIN indexes