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 1sFJ9K-0013Au-26 for pgsql-hackers@arkaria.postgresql.org; Thu, 06 Jun 2024 19:51:50 +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 1sFJ9H-003XQb-Pp for pgsql-hackers@arkaria.postgresql.org; Thu, 06 Jun 2024 19:51:48 +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 1sFJ9H-003XQS-Hl for pgsql-hackers@lists.postgresql.org; Thu, 06 Jun 2024 19:51:48 +0000 Received: from mail-il1-x131.google.com ([2607:f8b0:4864:20::131]) by makus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.94.2) (envelope-from ) id 1sFJ9F-00031l-TS for pgsql-hackers@postgresql.org; Thu, 06 Jun 2024 19:51:47 +0000 Received: by mail-il1-x131.google.com with SMTP id e9e14a558f8ab-3737dc4a669so5834205ab.0 for ; Thu, 06 Jun 2024 12:51:45 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1717703505; x=1718308305; 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=KfYZVKhGgB46/X5FfPG7ZGlU9NBaR9Io4hWndiyjryM=; b=AnMz2mflfXwFKEzVsy9XqMsKTY3gVdtWiqiLje7mKwL50zaGHHNtL5ulXGawsviQDW aYMZki72WkXqQmQ8yBrzk+gydazEXijUVF6rBN4aFx5lK2eY8InbDsZPvueRkDXZ+l7C FxqxNVUFNWC8MPu+susi3RdXxfCFQm9yzkm28iFStnNEw3ucgfE775qEoZuEtwzd+XB/ keTfPjak0LltFgHlD+WwUtftggYPIjv0dk8biKEWvY4QmeuWecFfwCPvpSkW/pJlfFcz rZuUf7nozdrt/dc43ZMcIex9J2sAiGVUak1ngzzGjFWp+kZC1J5Y3CPDxmt/nver2QpV uySw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1717703505; x=1718308305; 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=KfYZVKhGgB46/X5FfPG7ZGlU9NBaR9Io4hWndiyjryM=; b=Y5vEoxUw4K0gvqmxLScKLFLQot+Xo3pgIImW261gj+TAygblntpEEvpOY+e75qHma5 x/zmM7oLF4RazksZUXofiD0jTYZSL/UCKut8brRb391lHbBDMhZKwx0R60Tu5Poh5xjC CSzK98IYgrvGtG+dMsvKLJc3D2ynwEziZwzIUViH3nuXgAc3LZ9uTruFZINvgMLV1cGi dFPO39pRIEihB9wz70rooaXEGN/dnqxAm1UF7RhSCMHJM/xkamfcYLrcnrrP5eTqKcXj jRUYC7tjgyyqdkXqY+92NLqNJI5yUUeT3Ba0PntNV9MR30U3ut7n/6VRJ2Y1gjY/Uppa ZeSA== X-Forwarded-Encrypted: i=1; AJvYcCXXNgCK8MorxjdzJSooqCuDdaQVw3LO0vbkMe6UtSNmxAN6B4kJbTPOTfztnLxBC1wxjdkO3a/6diSyXStbLCDv0Z963JSSZSigeWA8 X-Gm-Message-State: AOJu0YzpwPAgftlEzzE98KPRB4R3dw/MCEJfzX2O/F42mfeDpRjp4uGX bTvxsX5hnkAOWUMpSQm2mWE8mFHxzwwjssseJGttDPi4/gIyCBnu X-Google-Smtp-Source: AGHT+IH4ZPV9Z4FADNVqYA4kl3C8nc4ZG6jG3BAgAokLlly751ohrFU5K31AGgWOjo+hI1mLYkf2jg== X-Received: by 2002:a92:cd81:0:b0:374:97b4:dbd1 with SMTP id e9e14a558f8ab-3758034c7dcmr8192485ab.18.1717703504960; Thu, 06 Jun 2024 12:51:44 -0700 (PDT) Received: from nathan (162-195-168-172.lightspeed.stlsmo.sbcglobal.net. [162.195.168.172]) by smtp.gmail.com with ESMTPSA id e9e14a558f8ab-374bc12e5e4sm4445975ab.5.2024.06.06.12.51.44 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Thu, 06 Jun 2024 12:51:44 -0700 (PDT) Date: Thu, 6 Jun 2024 14:51:42 -0500 From: Nathan Bossart To: Robert Haas Cc: "Imseih (AWS), Sami" , Tom Lane , Justin Pryzby , "pgsql-hackers@postgresql.org" Subject: Re: problems with "Shared Memory and Semaphores" section of docs Message-ID: References: <2463906.1715965795@sss.pgh.pa.us> <20240517174837.GB1918496@nathanxps13> <20240517192123.GA1933425@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, Jun 06, 2024 at 03:31:53PM -0400, Robert Haas wrote: > I don't really like making this a GUC, but what's the other option? > It's reasonable for people to want to ask the server how many > resources it will need to start, and -C is the only tool we have for > that right now. So I feel like this is a fair thing to do. Yeah, this is how I feel, too. > I do think the name could use some more thought, though. > semaphores_required would end up being the same kind of thing as > shared_memory_size_in_huge_pages, but the names seem randomly > different. If semaphores_required is right here, why isn't > shared_memory_required used there? Seems more like we ought to call > this semaphores or os_semaphores or num_semaphores or > num_os_semaphores or something. I'm fine with any of your suggestions. If I _had_ to pick one, I'd probably choose num_os_semaphores because it's the most descriptive. -- nathan