Re: pgsql: Move scanint8() to numutils.c

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Robert Haas <robertmhaas(at)gmail(dot)com>
Cc: Joe Conway <mail(at)joeconway(dot)com>, Peter Eisentraut <peter(at)eisentraut(dot)org>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: pgsql: Move scanint8() to numutils.c
Date: 2022-02-15 19:05:19
Message-ID: 3158140.1644951919@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-committers pgsql-hackers

Robert Haas <robertmhaas(at)gmail(dot)com> writes:
> On Tue, Feb 15, 2022 at 10:39 AM Joe Conway <mail(at)joeconway(dot)com> wrote:
>> scanint8() is exported, and this change breaks at least two extensions I
>> maintain.

> I don't have a particularly strong view on whether the underlying
> change was a good idea here, but the breakage you're talking about
> seems pretty easy to fix, unless I'm missing something? I think it
> would be a bad idea to make such a change in a minor release without
> concern for extension breakage, but in a new major release it doesn't
> seem like a problem to me.

Yeah, this seems well within our expectations for major-release
changes.

regards, tom lane

In response to

Browse pgsql-committers by date

  From Date Subject
Next Message Thomas Munro 2022-02-15 20:18:53 Re: pgsql: Track LLVM 15 changes.
Previous Message Joe Conway 2022-02-15 19:00:04 Re: pgsql: Move scanint8() to numutils.c

Browse pgsql-hackers by date

  From Date Subject
Next Message Bharath Rupireddy 2022-02-15 19:31:02 Re: pg_walinspect - a new extension to get raw WAL data and WAL stats
Previous Message Joe Conway 2022-02-15 19:00:04 Re: pgsql: Move scanint8() to numutils.c