Re: pgsql: Move scanint8() to numutils.c - Mailing list pgsql-hackers

From Peter Eisentraut
Subject Re: pgsql: Move scanint8() to numutils.c
Date
Msg-id 288c1f67-ba83-dec4-5830-c7cc7762da39@enterprisedb.com
Whole thread Raw
In response to Re: pgsql: Move scanint8() to numutils.c  (Joe Conway <mail@joeconway.com>)
Responses Re: pgsql: Move scanint8() to numutils.c  (Robert Haas <robertmhaas@gmail.com>)
List 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).



pgsql-hackers by date:

Previous
From: Peter Eisentraut
Date:
Subject: Re: bailing out in tap tests nearly always a bad idea
Next
From: "osumi.takamichi@fujitsu.com"
Date:
Subject: RE: Optionally automatically disable logical replication subscriptions on error