Re: problems with "Shared Memory and Semaphores" section of docs - Mailing list pgsql-hackers

From Nathan Bossart
Subject Re: problems with "Shared Memory and Semaphores" section of docs
Date
Msg-id 20240517192123.GA1933425@nathanxps13
Whole thread Raw
In response to Re: problems with "Shared Memory and Semaphores" section of docs  (Nathan Bossart <nathandbossart@gmail.com>)
Responses Re: problems with "Shared Memory and Semaphores" section of docs
List pgsql-hackers
On Fri, May 17, 2024 at 12:48:37PM -0500, Nathan Bossart wrote:
> On Fri, May 17, 2024 at 01:09:55PM -0400, Tom Lane wrote:
>> Nathan Bossart <nathandbossart@gmail.com> writes:
>>> At a bare minimum, we should probably fix the obvious problems, but I
>>> wonder if we could simplify this section a bit, too.
>> 
>> Yup.  "The definition of insanity is doing the same thing over and
>> over and expecting different results."  Time to give up on documenting
>> these things in such detail.  Anybody who really wants to know can
>> look at the source code.
> 
> Cool.  I'll at least fix the back-branches as-is, but I'll see about
> revamping this stuff for v18.

Attached is probably the absolute least we should do for the back-branches.

-- 
Nathan Bossart
Amazon Web Services: https://aws.amazon.com

Attachment

pgsql-hackers by date:

Previous
From: Mark Dilger
Date:
Subject: Re: [PATCH] Improve amcheck to also check UNIQUE constraint in btree index.
Next
From: Robert Haas
Date:
Subject: Re: Add new protocol message to change GUCs for usage with future protocol-only GUCs