Sameer Malve <malvesameer@gmail.com> writes:
> I am seeing in postgresql release notes that below bugs are fix in 9.6.x
> version but unable to find the details for about that bug .
If you want more detail than is in the release notes, look at the SGML
source for the notes to see the commit references, for example
<listitem>
<!--
Author: Noah Misch <noah@leadboat.com>
Branch: master [ab0ed6153] 2018-08-31 22:59:58 -0700
Branch: REL_11_STABLE Release: REL_11_0 [ee0ab2754] 2018-08-31 23:00:01 -0700
Branch: REL_10_STABLE [1664c8b30] 2018-08-31 23:00:01 -0700
Branch: REL9_6_STABLE [081e4104a] 2018-08-31 23:00:02 -0700
Branch: REL9_5_STABLE [e3eca937c] 2018-08-31 23:00:02 -0700
Branch: REL9_4_STABLE [20cd88857] 2018-08-31 23:00:03 -0700
-->
<para>
Fix unexpected timeouts when
using <varname>wal_sender_timeout</varname> on a slow server
(Noah Misch)
</para>
</listitem>
and then you can look at, eg,
https://git.postgresql.org/gitweb/?p=postgresql.git&a=commitdiff&h=081e4104a
(or do "git show 081e4104a" in a git checkout) to see the commit log
message and the actual code changes.
For the last year or so, the policy has been to include these commit
reference comments in every relevant branch's release-m.n.sgml file.
Before that you had to dig around a little, because in the interests
of space I only included them in the newest released branch. (So for
example the above is from the v10 branch; v11 was not yet released
so it had no release note for this.)
As Adrian mentions, grepping the result of "git log" is also a
good way to find relevant commits.
regards, tom lane
