Re: MultiXact\SLRU buffers configuration

From: Kyotaro Horiguchi <horikyota(dot)ntt(at)gmail(dot)com>
To: x4mmm(at)yandex-team(dot)ru
Cc: alvherre(at)alvh(dot)no-ip(dot)org, vignesh21(at)gmail(dot)com, amborodin86(at)gmail(dot)com, i(dot)lazarev(at)postgrespro(dot)ru, y(dot)sokolov(at)postgrespro(dot)ru, andres(at)anarazel(dot)de, thomas(dot)munro(at)gmail(dot)com, gilles(at)darold(dot)net, tomas(dot)vondra(at)enterprisedb(dot)com, tomas(dot)vondra(at)2ndquadrant(dot)com, aekorotkov(at)gmail(dot)com, a(dot)lubennikova(at)postgrespro(dot)ru, daniel(at)yesql(dot)se, pgsql-hackers(at)postgresql(dot)org
Subject: Re: MultiXact\SLRU buffers configuration
Date: 2024-02-29 01:59:44
Message-ID: 20240229.105944.773077833314087742.horikyota.ntt@gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

At Sat, 3 Feb 2024 22:32:45 +0500, "Andrey M. Borodin" <x4mmm(at)yandex-team(dot)ru> wrote in
> Here's the test draft. This test reliably reproduces sleep on CV when waiting next multixact to be filled into "members" SLRU.

By the way, I raised a question about using multiple CVs
simultaneously [1]. That is, I suspect that the current CV
implementation doesn't allow us to use multiple condition variables at
the same time, because all CVs use the same PCPROC member cvWaitLink
to accommodate different waiter sets. If this assumption is correct,
we should resolve the issue before spreading more uses of CVs.

[1] https://www.postgresql.org/message-id/20240227.150709.1766217736683815840.horikyota.ntt%40gmail.com

regards.

--
Kyotaro Horiguchi
NTT Open Source Software Center

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Masahiko Sawada 2024-02-29 02:47:51 Re: Making the initial and maximum DSA segment sizes configurable
Previous Message Andrei Lepikhov 2024-02-29 01:50:06 Re: POC, WIP: OR-clause support for indexes