Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1rF7K3-008PPP-PU for pgsql-hackers@arkaria.postgresql.org; Mon, 18 Dec 2023 06:41:52 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.94.2) (envelope-from ) id 1rF7K2-006mQe-FX for pgsql-hackers@arkaria.postgresql.org; Mon, 18 Dec 2023 06:41:50 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1rF7Hp-006izs-S0 for pgsql-hackers@lists.postgresql.org; Mon, 18 Dec 2023 06:39:34 +0000 Received: from mail.postgrespro.ru ([93.174.131.139]) by makus.postgresql.org with esmtps (TLS1.2) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1rF7Hm-00AxI9-18 for pgsql-hackers@postgresql.org; Mon, 18 Dec 2023 06:39:32 +0000 Received: from [192.168.1.37] (cm-27-145-164-60.revip12.asianet.co.th [27.145.164.60]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client did not present a certificate) (Authenticated sender: a.lepikhov@postgrespro.ru) by mail.postgrespro.ru (Postfix/587) with ESMTPSA id 09FE6E20E8C; Mon, 18 Dec 2023 09:39:25 +0300 (MSK) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=postgrespro.ru; s=mx2023; t=1702881566; bh=lgzY08/PDmhsnEpyDW/jvg9JSE5mE1JuhV9Cf2cDEKQ=; h=Message-ID:Date:User-Agent:Subject:To:References:From:In-Reply-To: From; b=lrYGi9/MrjE2m2VaYM/eMQNxaaGlqYVtQeHdyhDr8VgLZGwivp+eZIt5DZzYLJ1Pz x/zO0fJ/y1zTr7TwuhhWJZrB+I2WhtTX/5NduNqBikfOLWXWPh5bSbgy2RbylhirQT q2XXJapBnSEXgvI73Cat3qK7zY8vnk8eJLYqKfhSVilsq/kUEVADla+9CYUsdZcZcc tCpImdFHuN8gCQERZoxH0ZGXvrH1RdKJ1EarcmZIrb0A7bIAG3hG0P1DyNaPM2OJaQ KKwgW3ksWPI2NQ7D5RXtZS8vtWQR6mRVLN+kExOp25bgnlSgrnpl+UK4dx0rfJ0lEv jkWN7QBJVWA0g== Message-ID: Date: Mon, 18 Dec 2023 13:39:22 +0700 MIME-Version: 1.0 User-Agent: Mozilla Thunderbird Subject: Re: introduce dynamic shared memory registry To: Nathan Bossart , pgsql-hackers@postgresql.org References: <20231205034647.GA2705267@nathanxps13> Content-Language: en-US From: Andrei Lepikhov Organization: Postgres Professional In-Reply-To: <20231205034647.GA2705267@nathanxps13> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk On 5/12/2023 10:46, Nathan Bossart wrote: > I don't presently have any concrete plans to use this for anything, but I > thought it might be useful for extensions for caching, etc. and wanted to > see whether there was any interest in the feature. I am delighted that you commenced this thread. Designing extensions, every time I feel pain introducing one shared value or some global stat, the extension must be required to be loadable on startup only. It reduces the flexibility of even very lightweight extensions, which look harmful to use in a cloud. -- regards, Andrei Lepikhov Postgres Professional