Downloads
Home   >   mailing lists

Re: PG 18 beta1 release notes misses mention of pg_noreturn - Mailing list pgsql-hackers

From Steve Chavez
Subject Re: PG 18 beta1 release notes misses mention of pg_noreturn
Date
Msg-id CAGRrpzbk-FgW=Pr7ufRwS-wuG_8rgWgF5WLjTt4m3j3Y2Yi59g@mail.gmail.com
Whole thread Raw
In response to Re: PG 18 beta1 release notes misses mention of pg_noreturn  (Daniel Gustafsson <daniel@yesql.se>)
List pgsql-hackers
Tree view
Yes, otherwise I had to grep the commits in `git log` and find what's the correct way to use `pg_noreturn`. 
It's not a simple keyword replacement since the order has to change now:

Old: void my_worker(Datum main_arg) pg_attribute_noreturn();

New: pg_noreturn void my_worker(Datum main_arg);

I've added the link to the commit in the patch, which should be enough to infer the above.

How can I get this committed? Is the hacker mailing list the right place for release notes correction?

Best regards,
Steve Chavez

On Wed, 2 Jul 2025 at 11:24, Daniel Gustafsson <daniel@yesql.se> wrote:
> On 2 Jul 2025, at 04:51, Steve Chavez <steve@supabase.io> wrote:

> While updating an extension to support 18beta1, I stumbled on the removal of `pg_attribute_noreturn()` in favor of `pg_noreturn`, which wasn't mentioned in the release notes.

That admittedly seems like something worth including since it's otherwise not
documented anywhere.

--
Daniel Gustafsson

pgsql-hackers by date:

Previous
From: Ashutosh Bapat
Date:
Subject: Re: Adding basic NUMA awareness
Next
From: Dmitry Dolgov
Date:
Subject: Re: Adding basic NUMA awareness