| From: | Andres Freund <andres(at)anarazel(dot)de> |
|---|---|
| To: | Thomas Munro <thomas(dot)munro(at)gmail(dot)com> |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Noah Misch <noah(at)leadboat(dot)com>, pgsql-hackers(at)lists(dot)postgresql(dot)org |
| Subject: | Re: Remove last traces of HPPA support |
| Date: | 2024-07-31 22:38:51 |
| Message-ID: | 20240731223851.62rh7xqwqr4rzzto@awork3.anarazel.de |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Hi,
On 2024-08-01 10:09:07 +1200, Thomas Munro wrote:
> On Thu, Aug 1, 2024 at 7:07 AM Andres Freund <andres(at)anarazel(dot)de> wrote:
> > Note that I would like to add a user for S_LOCK_FREE(), to detect repeated
> > SpinLockRelease():
> > https://postgr.es/m/20240729182952.hua325647e2ggbsy%40awork3.anarazel.de
>
> What about adding a "magic" member in assertion builds? Here is my
> attempt at that, in 0002.
That changes the ABI, which we don't want, because it breaks using
extensions against a differently built postgres.
I don't really see a reason to avoid having S_LOCK_FREE(), am I missing
something? Previously the semaphore fallback was a reason, but that's gone
now...
Greetings,
Andres Freund
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Peter Smith | 2024-07-31 22:55:13 | Re: Logical Replication of sequences |
| Previous Message | Peter Smith | 2024-07-31 22:27:38 | Re: Logical Replication of sequences |