pg.ddx.io  pgsql-docs@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Laurenz Albe <laurenz.albe@cybertec.at>
To: Yong Huang <yong321@yahoo.com>
To: pgsql-docs@lists.postgresql.org, Michael Paquier <michael@paquier.xyz>
Subject: Re: postmaster.pid also contains shared memory key
Date: Sun, 01 Nov 2026 13:44:00 +0100
Message-ID: <753efd2b298df13383b4c57a57d965baac64aae7.camel@cybertec.at> (raw)
In-Reply-To: <662111745.874151.1793498212565@mail.yahoo.com>
References: <179313458417.1253.445225696660341760@wrigleys.postgresql.org>
	<auU0j2GdKLBQ1suV@paquier.xyz>
	<662111745.874151.1793498212565@mail.yahoo.com>

On Sun, 2026-11-01 at 01:56 +0000, Yong Huang wrote:
> On Friday, October 30, 2026 at 07:21:41 PM CDT, Michael Paquier <michael@paquier.xyz> wrote: 
> > On Tue, Oct 27, 2026 at 08:56:24PM +0000, PG Doc comments form wrote:
> > > 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?
> >
> > Would you like to write a patch?
>
> The proposed change is too trivial. I just want to inform the documentation team.
> Most readers won't care anyway. Thank you!

Nothing is too trivial.  I do care - here is a patch.

Yours,
Laurenz Albe

Attachments:

v1-0001-Improve-documentation-for-postmaster.pid.patch (text/x-patch, 1.2K) download From cac82bc180613f9097e941f4c7a44f09fee419dd Mon Sep 17 00:00:00 2001 From: Laurenz Albe <laurenz.albe@cybertec.at> Date: Sun, 1 Nov 2026 13:42:29 +0100 Subject: [PATCH v1] Improve documentation for postmaster.pid The description mentioned that the file contains the shared memory segment ID, but forgot to mention the shared memory segment key reported on the same line. This could cause confusion. Author: Laurenz Albe <laurenz.albe@cybertec.at> Reported-By: Yong Huang <yong321@yahoo.com> Discussion: https://postgr.es/m/179313458417.1253.445225696660341760%40wrigleys.postgresql.org --- doc/src/sgml/storage.sgml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/doc/src/sgml/storage.sgml b/doc/src/sgml/storage.sgml index 83de016eaa5..5612e9868a6 100644 --- a/doc/src/sgml/storage.sgml +++ b/doc/src/sgml/storage.sgml @@ -174,7 +174,7 @@ last started with</entry> Unix-domain socket directory path (could be empty), first valid listen_address (IP address or <literal>*</literal>, or empty if not listening on TCP), - and shared memory segment ID + and shared memory segment key and ID (this file is not present after server shutdown)</entry> </row> -- 2.56.0

view thread (8+ messages)  latest in thread

Message-ID: <753efd2b298df13383b4c57a57d965baac64aae7.camel@cybertec.at>
Permalink:  ../753efd2b298df13383b4c57a57d965baac64aae7.camel@cybertec.at/
Also on:    postgresql.org/message-id/753efd2b298df13383b4c57a57d965baac64aae7.camel@cybertec.at

 ·  · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients from your mail client; the link fills in
  the headers below: reply via email
  Some clients, webmail especially, drop In-Reply-To and References from
  a link, and the reply then starts a new thread: use the mbox below.

  To: pgsql-docs@postgresql.org
  Cc: laurenz.albe@cybertec.at, yong321@yahoo.com, michael@paquier.xyz
  Subject: Re: postmaster.pid also contains shared memory key
  In-Reply-To: <753efd2b298df13383b4c57a57d965baac64aae7.camel@cybertec.at>
  References: <179313458417.1253.445225696660341760@wrigleys.postgresql.org> <auU0j2GdKLBQ1suV@paquier.xyz> <662111745.874151.1793498212565@mail.yahoo.com> <753efd2b298df13383b4c57a57d965baac64aae7.camel@cybertec.at>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox