| From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
|---|---|
| To: | Peter Eisentraut <peter(dot)eisentraut(at)enterprisedb(dot)com> |
| Cc: | Joe Conway <mail(at)joeconway(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: pgsql: Move scanint8() to numutils.c |
| Date: | 2022-02-16 13:24:31 |
| Message-ID: | CA+TgmoaQQS14k0nEB9QMpm6mvu+5uZdqFd4kNdO3GBEGeW2qyQ@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-committers pgsql-hackers |
On Wed, Feb 16, 2022 at 6:09 AM Peter Eisentraut
<peter(dot)eisentraut(at)enterprisedb(dot)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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Julien Rouhaud | 2022-02-16 15:42:46 | Re: pgsql: Move scanint8() to numutils.c |
| Previous Message | Christoph Berg | 2022-02-16 12:38:51 | Re: pgsql: Add TAP test to automate the equivalent of check_guc |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Ashutosh Bapat | 2022-02-16 13:40:53 | Re: postgres_fdw and skip locked |
| Previous Message | Jim Mlodgenski | 2022-02-16 13:17:13 | Re: support for CREATE MODULE |