pg.ddx.io  pgsql-hackers@postgresql.org mailing list archive  

help / color / mirror / Atom feed

From: Nathan Bossart <nathandbossart@gmail.com>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: pgsql-hackers@postgresql.org
Subject: Re: small cleanup for s_lock.h
Date: Mon, 28 Sep 2026 13:54:54 -0500
Message-ID: <arq3_vD_TSGBhhtQ@nathan> (raw)
In-Reply-To: <arbhohGoRM2Phzm4@nathan>
References: <afkUeI7UhacZ5ZFm@nathan>
	<369933.1777933007@sss.pgh.pa.us>
	<afoWBgsygtkCNCRQ@nathan>
	<532705.1778000169@sss.pgh.pa.us>
	<afovdi61nybDRbC3@nathan>
	<afz5FHWr6rOB7bsL@nathan>
	<af0AKUfzjGDvQdBk@nathan>
	<af0D6fhLfVmG2fr7@nathan>
	<arbhohGoRM2Phzm4@nathan>

On Fri, Sep 25, 2026 at 04:03:30PM -0500, Nathan Bossart wrote:
> I've committed v5-{0001,0002} and attached a rebased version of 0003.
> Besides fixing some small things discovered during LLM review, I decided to
> remove the restriction that only one of TAS or S_LOCK can be defined.
> Having both doesn't break anything; we just use the platform's S_LOCK in
> that case.

I've now committed 0003.

-- 
nathan

view thread (14+ messages)

Message-ID: <arq3_vD_TSGBhhtQ@nathan>
Permalink:  ../arq3_vD_TSGBhhtQ@nathan/
Also on:    postgresql.org/message-id/arq3_vD_TSGBhhtQ@nathan

copy link · copy postgr.es

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 using the --to and --cc options:
  reply via email

  To: pgsql-hackers@postgresql.org
  Cc: nathandbossart@gmail.com, tgl@sss.pgh.pa.us
  Subject: Re: small cleanup for s_lock.h
  In-Reply-To: <arq3_vD_TSGBhhtQ@nathan>

* 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