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

From: Peter Eisentraut <peter(dot)eisentraut(at)enterprisedb(dot)com>
To: Joe Conway <mail(at)joeconway(dot)com>, Robert Haas <robertmhaas(at)gmail(dot)com>
Cc: PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: pgsql: Move scanint8() to numutils.c
Date: 2022-02-16 11:09:49
Message-ID: 288c1f67-ba83-dec4-5830-c7cc7762da39@enterprisedb.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-committers pgsql-hackers

On 15.02.22 20:00, Joe Conway wrote:
> I'm not saying it is hard to fix, but it seems a bit cavalier to not
> even discuss the potential for breakage. If nothing else we should flag
> this as something for the release notes.

I don't think we have ever systematically release-noted backend API
changes. I don't know whether that would be useful, but a complete
treatment would be a significant effort (speaking from experience of
porting the mentioned pglogical between major releases).

In response to

Responses

Browse pgsql-committers by date

  From Date Subject
Next Message John Naylor 2022-02-16 12:36:13 pgsql: Add missing TYPEALIGN macros
Previous Message Heikki Linnakangas 2022-02-16 10:02:02 pgsql: Fix read beyond buffer bug introduced by the split xlog.c patch.

Browse pgsql-hackers by date

  From Date Subject
Next Message osumi.takamichi@fujitsu.com 2022-02-16 11:19:06 RE: Optionally automatically disable logical replication subscriptions on error
Previous Message Peter Eisentraut 2022-02-16 11:03:21 Re: bailing out in tap tests nearly always a bad idea