Re: pgsql: Remove unused wait events.

From: Robert Haas <robertmhaas(at)gmail(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Amit Kapila <akapila(at)postgresql(dot)org>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: pgsql: Remove unused wait events.
Date: 2021-10-25 17:10:25
Message-ID: CA+TgmoZ2W5Pqq19kzN5K-Boveq0u1v5az7wFJcUhHdZ18aw7_A@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-committers pgsql-hackers

On Mon, Oct 25, 2021 at 12:38 PM Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> Um ... the removed symbols were at the end of the WaitEventIO enum,
> so is there really an ABI break? I suppose if an extension contains
> actual references to the removed symbols, it would fail to recompile,
> which'd be annoying for a released branch.

I think that you're right. I believe one of the two extensions I know
about hopes that values won't be renumbered or become invalid across
minor releases, and the other contains specific references to these
particular constants.

Now of course it is always arguable whether or not anything that some
extension is doing ought to be deemed an acceptable use of the
facilities provided by core, and how much stability ought to be
guaranteed. But while I agree it's good to remove unused stuff in the
master, it doesn't seem like we really need to back-patch it.

--
Robert Haas
EDB: http://www.enterprisedb.com

In response to

Responses

Browse pgsql-committers by date

  From Date Subject
Next Message Tom Lane 2021-10-25 17:18:26 Re: pgsql: Remove unused wait events.
Previous Message Tom Lane 2021-10-25 16:38:38 Re: pgsql: Remove unused wait events.

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2021-10-25 17:14:19 Re: pg_dump versus ancient server versions
Previous Message Tom Lane 2021-10-25 17:09:43 Re: pg_dump versus ancient server versions