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

From Robert Haas
Subject Re: pgsql: Move scanint8() to numutils.c
Date
Msg-id CA+TgmoaQQS14k0nEB9QMpm6mvu+5uZdqFd4kNdO3GBEGeW2qyQ@mail.gmail.com
Whole thread Raw
In response to Re: pgsql: Move scanint8() to numutils.c  (Peter Eisentraut <peter.eisentraut@enterprisedb.com>)
Responses Re: pgsql: Move scanint8() to numutils.c
List pgsql-hackers
On Wed, Feb 16, 2022 at 6:09 AM Peter Eisentraut
<peter.eisentraut@enterprisedb.com> wrote:
> 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).

Personally, I don't think I would ever have used such a thing if it
had existed, because looking through the git history seems more
efficient to me. The release notes can be wrong or can fail to contain
enough information to fix whatever issue I've encountered, but the
offending commit always tells the real story. It sounds like Joe may
feel differently which is fair enough; I can only speak to my own
experience.

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



pgsql-hackers by date:

Previous
From: Jim Mlodgenski
Date:
Subject: Re: support for CREATE MODULE
Next
From: Ashutosh Bapat
Date:
Subject: Re: postgres_fdw and skip locked