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 1rNleX-00FRxP-AV for pgsql-hackers@arkaria.postgresql.org; Thu, 11 Jan 2024 03:22:45 +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 1rNleW-008xlb-FF for pgsql-hackers@arkaria.postgresql.org; Thu, 11 Jan 2024 03:22:44 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1rNleW-008xlT-5t for pgsql-hackers@lists.postgresql.org; Thu, 11 Jan 2024 03:22:44 +0000 Received: from mail-io1-xd33.google.com ([2607:f8b0:4864:20::d33]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.94.2) (envelope-from ) id 1rNleT-000w9d-Jp for pgsql-hackers@postgresql.org; Thu, 11 Jan 2024 03:22:43 +0000 Received: by mail-io1-xd33.google.com with SMTP id ca18e2360f4ac-7bedd61c587so79999539f.2 for ; Wed, 10 Jan 2024 19:22:41 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1704943360; x=1705548160; darn=postgresql.org; h=in-reply-to:content-disposition:mime-version:references:message-id :subject:cc:to:from:date:from:to:cc:subject:date:message-id:reply-to; bh=emVSGZWSDvHyjTJkFwbf3mtxqv7rItmgkSupEAgSB8o=; b=W1lxEVTTowrAopeZRhZpAYxbgxJ0DyGRM7S5nivkj3UkQuE0kYWn2PYGnvYOQRtHFP S3CmDA9FfsmmaofZcBCruiDCIxUPEl2QFW0yge0fti7ASFNaGVzPivPX4d5AVWK0mLTw L1EVTU5x/dJILmmdF0Aleid3yW7pU3e9+PDqfElkGb8WABgDuMlffh7SemJAOZnXfkfz idNDasSOV7bmqhMB1ye6EUnpPoAcu3AVZo42kNrxLj44UGK2A54g7aZHuMMJ1JDYTtWp a4iJZI4dQmzvwyBfyrQM5Ul0jlExFfpsZ74OBAOPMFco9V4JYIkDWiq3blyRhAXzOFk1 arNg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1704943360; x=1705548160; h=in-reply-to:content-disposition:mime-version:references:message-id :subject:cc:to:from:date:x-gm-message-state:from:to:cc:subject:date :message-id:reply-to; bh=emVSGZWSDvHyjTJkFwbf3mtxqv7rItmgkSupEAgSB8o=; b=ntbfd15xo7jVoSNc9zumSn9xRh7B80362F+vISPD65hurNfMTjExxESRBElYy4dPSW tEI0lYFDec/CabKlGz/rmqWXeC3RKEftZ7C/+Q+3tiiEOX2g+Xl9+GdcojNMHi4eB6gQ 5b9tXUjIkRjb00yMWUDHfNx7VY2GWjM7dBu4G5lpXLYFL9fr3lyHB6Lrb30xi9A8mqtk 9qNcQKqMYmBDdNVMcI7SoEuXTbio+hFNCitlCJkwhDMlRuECO1x26Q7jisUSygLNnnct birOpHG/9bb+Qhsci8N5IVhlroqZCcKHEO2bMvdj3XbDMSz5y/JC1gZV8PZX71i4AavQ lPPg== X-Gm-Message-State: AOJu0Yz3NuayDfK8sFwEL+1sdsgtDdhtiDbR1ULiD0UvtI4Jl1lgECzu sQP2sBIq5Ujd30735cllCqxn3LDfOrI= X-Google-Smtp-Source: AGHT+IFJpkpvPtskzqX8KYUxzB8ehHzCTSqUIxg4rJuvmsZc7DPR71G/g6wzqoi0F85wtEYfEdtufw== X-Received: by 2002:a5d:9a86:0:b0:7be:db69:b1f2 with SMTP id c6-20020a5d9a86000000b007bedb69b1f2mr686375iom.39.1704943359823; Wed, 10 Jan 2024 19:22:39 -0800 (PST) Received: from nathanxps13 (162-195-168-172.lightspeed.stlsmo.sbcglobal.net. [162.195.168.172]) by smtp.gmail.com with ESMTPSA id cl13-20020a0566383d0d00b0046e29c56401sm71411jab.0.2024.01.10.19.22.39 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Wed, 10 Jan 2024 19:22:39 -0800 (PST) Date: Wed, 10 Jan 2024 21:22:37 -0600 From: Nathan Bossart To: Andrei Lepikhov Cc: Bharath Rupireddy , Robert Haas , pgsql-hackers@postgresql.org Subject: Re: introduce dynamic shared memory registry Message-ID: <20240111032237.GB3376512@nathanxps13> References: <20231220160324.GB833819@nathanxps13> <20240102162054.GB955987@nathanxps13> <20240102224907.GA1246933@nathanxps13> <20240106163516.GB2435448@nathanxps13> <20240108171627.GA2611898@nathanxps13> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk On Thu, Jan 11, 2024 at 09:50:19AM +0700, Andrei Lepikhov wrote: > On 9/1/2024 00:16, Nathan Bossart wrote: >> On Mon, Jan 08, 2024 at 10:53:17AM +0530, Bharath Rupireddy wrote: >> > 2. FWIW, I'd like to call this whole feature "Support for named DSM >> > segments in Postgres". Do you see anything wrong with this? >> >> Why do you feel it should be renamed? I don't see anything wrong with it, >> but I also don't see any particular advantage with that name compared to >> "dynamic shared memory registry." > It is not a big issue, I suppose. But for me personally (as not a native > English speaker), the label "Named DSM segments" seems more straightforward > to understand. That is good to know, thanks. I see that it would also align better with RequestNamedLWLockTranche/GetNamedLWLockTranche. -- Nathan Bossart Amazon Web Services: https://aws.amazon.com