pgsql: Release notes for 9.6.5, 9.5.9, 9.4.14, 9.3.19, 9.2.23.

On Sun, Aug 27, 2017 at 6:35 PM, Tom Lane <tgl@sss.pgh.pa.us> wrote:

Release notes for 9.6.5, 9.5.9, 9.4.14, 9.3.19, 9.2.23.

Branch
------
master

Details
-------

https://git.postgresql.org/pg/commitdiff/f97c55c708a6fbcb675be6fbb94af3038733dfa4

Modified Files
--------------
doc/src/sgml/release-9.2.sgml | 139 +++++++++++++++++++++++++++++++++++++
doc/src/sgml/release-9.3.sgml | 140 +++++++++++++++++++++++++++++++++++++
doc/src/sgml/release-9.4.sgml | 156

++++++++++++++++++++++++++++++++++++++++++

doc/src/sgml/release-9.5.sgml | 146

+++++++++++++++++++++++++++++++++++++++

doc/src/sgml/release-9.6.sgml | 17 -----
5 files changed, 581 insertions(+), 17 deletions(-)

I wonder why I was not marked as author of the "pg_restore" fix if what you
pushed [1]https://git.postgresql.org/gitweb/?p=postgresql.git;a=commitdiff;h=b1c2d76a2fcef812af0be3343082414d401909c8 is exactly what the patch I've sent [2]/messages/by-id/CAFcNs+pjuv0JL_x4+=71TPUPjdLHOXA4YfT32myj_OrrZb4ohA@mail.gmail.com.

Regards,

[1]: https://git.postgresql.org/gitweb/?p=postgresql.git;a=commitdiff;h=b1c2d76a2fcef812af0be3343082414d401909c8
https://git.postgresql.org/gitweb/?p=postgresql.git;a=commitdiff;h=b1c2d76a2fcef812af0be3343082414d401909c8
[2]: /messages/by-id/CAFcNs+pjuv0JL_x4+=71TPUPjdLHOXA4YfT32myj_OrrZb4ohA@mail.gmail.com
/messages/by-id/CAFcNs+pjuv0JL_x4+=71TPUPjdLHOXA4YfT32myj_OrrZb4ohA@mail.gmail.com

--
Fabrízio de Royes Mello
Consultoria/Coaching PostgreSQL

=?UTF-8?Q?Fabr=C3=ADzio_de_Royes_Mello?= <fabriziomello@gmail.com> writes:

On Sun, Aug 27, 2017 at 6:35 PM, Tom Lane <tgl@sss.pgh.pa.us> wrote:

Release notes for 9.6.5, 9.5.9, 9.4.14, 9.3.19, 9.2.23.

I wonder why I was not marked as author of the "pg_restore" fix if what you
pushed [1] is exactly what the patch I've sent [2].

Oh ... by the time I got done investigating what was happening and
deciding what would be the cleanest fix, I'd forgotten that what
I ended up with was the same actual code change as what you proposed
initially. The comment changes are a not-insubstantial part of the
fix, IMO, but still I should have given you more than just reporter's
credit in the commit message. Sorry about that, will change the
release notes.

regards, tom lane

--
Sent via pgsql-committers mailing list (pgsql-committers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-committers

On Mon, Aug 28, 2017 at 12:29 PM, Tom Lane <tgl@sss.pgh.pa.us> wrote:

=?UTF-8?Q?Fabr=C3=ADzio_de_Royes_Mello?= <fabriziomello@gmail.com> writes:

On Sun, Aug 27, 2017 at 6:35 PM, Tom Lane <tgl@sss.pgh.pa.us> wrote:

Release notes for 9.6.5, 9.5.9, 9.4.14, 9.3.19, 9.2.23.

I wonder why I was not marked as author of the "pg_restore" fix if what

you

pushed [1] is exactly what the patch I've sent [2].

Oh ... by the time I got done investigating what was happening and
deciding what would be the cleanest fix, I'd forgotten that what
I ended up with was the same actual code change as what you proposed
initially. The comment changes are a not-insubstantial part of the
fix, IMO, but still I should have given you more than just reporter's
credit in the commit message. Sorry about that, will change the
release notes.

Thanks... I did suspected something like that had happened.

Regards,

--
Fabrízio de Royes Mello
Consultoria/Coaching PostgreSQL