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 1rOLZa-003Pqk-Ma for pgsql-hackers@arkaria.postgresql.org; Fri, 12 Jan 2024 17:44:03 +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 1rOLZZ-004HEf-HC for pgsql-hackers@arkaria.postgresql.org; Fri, 12 Jan 2024 17:44:01 +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 1rOLZZ-004HEQ-4N for pgsql-hackers@lists.postgresql.org; Fri, 12 Jan 2024 17:44:01 +0000 Received: from pitta.toroid.org ([2a01:4f8:171:16c9::2]) by makus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1rOLZR-001DJM-JT for pgsql-hackers@postgresql.org; Fri, 12 Jan 2024 17:43:59 +0000 Received: from kathal.lweshal.in (unknown [10.2.1.2]) by pitta.toroid.org (Postfix) with ESMTP id 3D2FCFA37A4; Fri, 12 Jan 2024 18:43:50 +0100 (CET) DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=toroid.org; s=mail; t=1705081430; bh=pR1hG6qr1JAkTlhDbj9JE3D3dp5g03Q7H+96xTcin1A=; h=Date:From:To:Cc:Subject:References:In-Reply-To:From; b=XfAnb7G+vKvrtYyChrFcrkefULGu4DUHxIc72uRNSRqHTnH2JDACkOGtc9L2R+TIl OJ25x+Jebz72nVB+4SW4TSWuViSDwpSDkhGx8oHVgDVFIg6zlwu4YMRp1kKmDcD7vj Jxu7XM0YBOCbD2LHEUxI6IgCHtORulyf00sTm3g/mT3r+v4jobKyf/q3+OGA4FlIfk n/92Dl8Y5n9E+jVRrH1JizczDfq/KC02vOT8p3jPtwzOufmXTnxVfLqKLDm4U1wYpY G6vNnpauPFl4/EtMkhmFLgVtleJSdJxQZxMZf6aI6E2wnoObu+Xa9V3mEhimf/3Kp3 qlDKMpxce7tZA== Received: from ams by kathal.lweshal.in with local (Exim 4.96) (envelope-from ) id 1rOLZK-002MO6-2l; Fri, 12 Jan 2024 23:13:46 +0530 Date: Fri, 12 Jan 2024 23:13:46 +0530 From: Abhijit Menon-Sen To: Nathan Bossart Cc: Bharath Rupireddy , Michael Paquier , Robert Haas , pgsql-hackers@postgresql.org Subject: Re: introduce dynamic shared memory registry Message-ID: References: <20240102162054.GB955987@nathanxps13> <20240102224907.GA1246933@nathanxps13> <20240106163516.GB2435448@nathanxps13> <20240108171627.GA2611898@nathanxps13> <20240112172152.GA3803561@nathanxps13> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <20240112172152.GA3803561@nathanxps13> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk At 2024-01-12 11:21:52 -0600, nathandbossart@gmail.com wrote: > > From: Nathan Bossart > Date: Thu, 11 Jan 2024 21:55:25 -0600 > Subject: [PATCH v6 1/3] reorganize shared memory and lwlocks documentation > > --- > doc/src/sgml/xfunc.sgml | 182 +++++++++++++++++++++++++--------------- > 1 file changed, 114 insertions(+), 68 deletions(-) > > diff --git a/doc/src/sgml/xfunc.sgml b/doc/src/sgml/xfunc.sgml > index 89116ae74c..0ba52b41d4 100644 > --- a/doc/src/sgml/xfunc.sgml > +++ b/doc/src/sgml/xfunc.sgml > @@ -3397,90 +3397,136 @@ CREATE FUNCTION make_array(anyelement) RETURNS anyarray > > > […] > - from your shmem_request_hook. > - > - > - LWLocks are reserved by calling: > + Each backend sould obtain a pointer to the reserved shared memory by sould → should > + Add-ins can reserve LWLocks on server startup. Like with shared memory, (Would "As with shared memory" read better? Maybe, but then again maybe it should be left alone because you also write "Unlike with" elsewhere.) -- Abhijit