Re: tupconvert.c API change in v10 release notes

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Bruce Momjian <bruce(at)momjian(dot)us>
Cc: Justin Pryzby <pryzby(at)telsasoft(dot)com>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: tupconvert.c API change in v10 release notes
Date: 2017-09-08 21:00:18
Message-ID: 30636.1504904418@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Bruce Momjian <bruce(at)momjian(dot)us> writes:
> On Wed, Jul 19, 2017 at 12:39:07PM -0400, Tom Lane wrote:
>> Yeah, I see nothing about 3f902354b in release-10.sgml either.
>> We've had varying policies over the years about whether to mention
>> internal API changes in the release notes or not, but this one
>> I think does belong there, since it's a silent API break rather
>> than one that would easily be caught due to compiler errors.
>> Bruce, did you have any specific reasoning for leaving it out?

> I doubt I saw that sentence in the paragraph. For long text like that,
> I am usually looking for "BACKWARDS INCOMPATIBLE CHANGE" or something
> like that. Sorry I missed it.

I added something about this to the notes.

regards, tom lane

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2017-09-08 21:09:37 Re: PoC plpgsql - possibility to force custom or generic plan
Previous Message Merlin Moncure 2017-09-08 20:38:17 Re: PoC plpgsql - possibility to force custom or generic plan