From: | Nathan Bossart <nathandbossart(at)gmail(dot)com> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | "Imseih (AWS), Sami" <simseih(at)amazon(dot)com>, Justin Pryzby <pryzby(at)telsasoft(dot)com>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: problems with "Shared Memory and Semaphores" section of docs |
Date: | 2024-05-17 19:21:23 |
Message-ID: | 20240517192123.GA1933425@nathanxps13 |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | 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(at)gmail(dot)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 | Content-Type | Size |
---|---|---|
v1-0001-fix-kernel-resources-docs-on-back-branches.patch | text/x-diff | 3.0 KB |
From | Date | Subject | |
---|---|---|---|
Next Message | Robert Haas | 2024-05-17 19:24:26 | Re: Add new protocol message to change GUCs for usage with future protocol-only GUCs |
Previous Message | Mark Dilger | 2024-05-17 19:10:10 | Re: [PATCH] Improve amcheck to also check UNIQUE constraint in btree index. |