Mention fix for bug #1916 in release notes for affected versions.

doc/src/sgml/release.sgml

 <!--
-$PostgreSQL: pgsql/doc/src/sgml/release.sgml,v 1.379 2005/09/27 23:32:38 momjian Exp $
+$PostgreSQL: pgsql/doc/src/sgml/release.sgml,v 1.380 2005/09/28 21:22:12 tgl Exp $
 
 Typical markup:
 
@@ -2039,10 +2039,12 @@ failures when a crash occurs shortly after <command>CREATE
 DATABASE</>.</para></listitem>
 <listitem><para>Handle consecutive embedded newlines in <command>COPY</>
 CSV-mode input</para></listitem>
-<listitem><para>Further fixes for <literal>x FULL JOIN y ON true</> corner
-cases</para></listitem>
 <listitem><para>Fix <function>date_trunc(week)</> for dates near year
 end</para></listitem>
+<listitem><para>Fix planning problem with outer-join ON clauses that reference
+only the inner-side relation</para></listitem>
+<listitem><para>Further fixes for <literal>x FULL JOIN y ON true</> corner
+cases</para></listitem>
 <listitem><para>Fix overenthusiastic optimization of <literal>x IN (SELECT
 DISTINCT ...)</> and related cases</para></listitem>
 <listitem><para>Fix mis-planning of queries with small <literal>LIMIT</>
@@ -4806,6 +4808,8 @@ length when using a multiple-byte character set (Yoshiyuki Asaba)</para>
 <para>In prior releases, the padding of <type>CHAR()</> was incorrect
 because it only padded to the specified number of bytes without
 considering how many characters were stored.</para></listitem>
+<listitem><para>Fix planning problem with outer-join ON clauses that reference
+only the inner-side relation</para></listitem>
 <listitem><para>Further fixes for <literal>x FULL JOIN y ON true</> corner
 cases</para></listitem>
 <listitem><para>Make <function>array_in</> and <function>array_recv</> more