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.98.2) (envelope-from ) id 1xMNd0-00000001zq2-04Ih for pgsql-docs@arkaria.postgresql.org; Thu, 29 Oct 2026 10:45:02 +0000 Received: from localhost ([127.0.0.1]:40284 helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.98.2) (envelope-from ) id 1xMNcz-000000041Gc-2EL7 for pgsql-docs@arkaria.postgresql.org; Thu, 29 Oct 2026 10:45:01 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]:55452) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.98.2) (envelope-from ) id 1xLoEG-0000000C4Oh-3nZq for pgsql-docs@lists.postgresql.org; Tue, 27 Oct 2026 20:57:08 +0000 Received: from mahout.postgresql.org ([2001:4800:3e1:1::227]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.98.2) (envelope-from ) id 1xLoEE-00000001IKd-1MYj for pgsql-docs@lists.postgresql.org; Tue, 27 Oct 2026 20:57:08 +0000 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=postgresql.org; s=20171124; h=Message-ID:Date:Reply-To:Cc:From:To:Subject: Content-Transfer-Encoding:MIME-Version:Content-Type:Sender:Content-ID: Content-Description:In-Reply-To:References; bh=N/ZNEVFN6hhpomNgF2vR5lzHGwt5uhfhBW9/yIWsrDA=; b=vjlBbxh1k1/4uUFneSAxFiiuNM irgniUJDpDPJ+FLvaJvkhcyL0Y2E8OTyCo0sbhbmPlCBK1xrOER/HnZOMqbo3Rl3ZngHKUIK2TZPL ZhENYV6wHbxR/xcpHXI69lXlpy2gVPprxRJUMmVdZ5QEhKxpvr6drgNgPbjVMnSJXfguKsIbG8zuz Lt4M7FVmIUtUGTqPKIl+dLmXaWSob5nqpCoGgCnxb0C4fwiFZjee36ycOt2rLkU3G2mwPl75NYxJ2 4CQevGrk4n4+9M48GTiWQMTe64QcRx4QtazV04XwTSAbktZUhCMtflKaLv559Prayz/pqls6atd/5 FzVb6FdQ==; Received: from wrigleys.postgresql.org ([2a02:16a8:dc51::60]) by mahout.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.98.2) (envelope-from ) id 1xLoED-00000003cEw-06Oc for pgsql-docs@lists.postgresql.org; Tue, 27 Oct 2026 20:57:05 +0000 Received: from localhost ([127.0.0.1] helo=wrigleys.postgresql.org) by wrigleys.postgresql.org with esmtp (Exim 4.98.2) (envelope-from ) id 1xLoEA-00000003C8w-41rm for pgsql-docs@lists.postgresql.org; Tue, 27 Oct 2026 20:57:03 +0000 Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable Subject: postmaster.pid also contains shared memory key To: pgsql-docs@lists.postgresql.org From: PG Doc comments form Cc: yong321@yahoo.com Reply-To: yong321@yahoo.com, pgsql-docs@lists.postgresql.org Date: Tue, 27 Oct 2026 20:56:24 +0000 Message-ID: <179313458417.1253.445225696660341760@wrigleys.postgresql.org> X-Auto-Response-Suppress: All Auto-Submitted: auto-generated List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk The following documentation comment has been logged on the website: Page: https://www.postgresql.org/docs/18/storage-file-layout.html Description: On this page, postmaster.pid is said to contain "shared memory segment ID". It would be better to say "shared memory segment key and ID". The second last line has two numbers, which are the shared memory segment key (in decimal instead of hex) and ID, respectively. This can be verified with `ipcs -m'. If you only say "ID", readers may ask, Which one is the ID?