pg.ddx.io  pgsql-committers@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Julien Rouhaud <rjuju123@gmail.com>
To: Robert Haas <robertmhaas@gmail.com>
Cc: Peter Eisentraut <peter.eisentraut@enterprisedb.com>
Cc: Joe Conway <mail@joeconway.com>
Cc: PostgreSQL-development <pgsql-hackers@postgresql.org>
Subject: Re: pgsql: Move scanint8() to numutils.c
Date: Wed, 16 Feb 2022 23:42:46 +0800
Message-ID: <20220216154246.s2zbaakmzmurozvs@jrouhaud> (raw)
In-Reply-To: <CA+TgmoaQQS14k0nEB9QMpm6mvu+5uZdqFd4kNdO3GBEGeW2qyQ@mail.gmail.com>
References: <E1nJijU-0000fr-0S@gemulon.postgresql.org>
	<58cca3e9-53b8-e824-7cd4-6e59b4e242b1@joeconway.com>
	<CA+TgmobLY=ZcvD9cLnhA92ATnEfNHgfEDM4MUCsRADH9td+mrw@mail.gmail.com>
	<77f5b16f-cabd-e7e2-db9e-e3e41ff8eec6@joeconway.com>
	<288c1f67-ba83-dec4-5830-c7cc7762da39@enterprisedb.com>
	<CA+TgmoaQQS14k0nEB9QMpm6mvu+5uZdqFd4kNdO3GBEGeW2qyQ@mail.gmail.com>

Hi,

On Wed, Feb 16, 2022 at 08:24:31AM -0500, Robert Haas wrote:
> 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.

Agreed.  I have been maintaining extensions for quite some time and the commit
log (and possibly the referenced discussions) always contains everything needed
to fix whatever code is broken with all the important details.  I also try to
rebuild my extensions regularly against the current HEAD, so at the time the
release notes are written they wouldn't be of any use anyway.

The only reason I see to have something in the release notes would be to warn
about a problematic API change, which doesn't result in hard compilation
failure or something mostly immediate like that.





view thread (8+ messages)

Message-ID: <20220216154246.s2zbaakmzmurozvs@jrouhaud>
Permalink:  ../20220216154246.s2zbaakmzmurozvs@jrouhaud/
Also on:    postgresql.org/message-id/20220216154246.s2zbaakmzmurozvs@jrouhaud

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients from your mail client; the link fills in
  the headers below: reply via email
  Some clients, webmail especially, drop In-Reply-To and References from
  a link, and the reply then starts a new thread: use the mbox below.

  To: pgsql-committers@postgresql.org
  Cc: rjuju123@gmail.com, robertmhaas@gmail.com, peter.eisentraut@enterprisedb.com, mail@joeconway.com, pgsql-hackers@postgresql.org
  Subject: Re: pgsql: Move scanint8() to numutils.c
  In-Reply-To: <20220216154246.s2zbaakmzmurozvs@jrouhaud>
  References: <E1nJijU-0000fr-0S@gemulon.postgresql.org> <58cca3e9-53b8-e824-7cd4-6e59b4e242b1@joeconway.com> <CA+TgmobLY=ZcvD9cLnhA92ATnEfNHgfEDM4MUCsRADH9td+mrw@mail.gmail.com> <77f5b16f-cabd-e7e2-db9e-e3e41ff8eec6@joeconway.com> <288c1f67-ba83-dec4-5830-c7cc7762da39@enterprisedb.com> <CA+TgmoaQQS14k0nEB9QMpm6mvu+5uZdqFd4kNdO3GBEGeW2qyQ@mail.gmail.com> <20220216154246.s2zbaakmzmurozvs@jrouhaud>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox