Commit 2af664e7 authored by Tom Lane's avatar Tom Lane

Fix broken markup.

parent 51b2f8ba
<!-- <!--
$PostgreSQL: pgsql/doc/src/sgml/release.sgml,v 1.331 2005/04/02 03:42:41 momjian Exp $ $PostgreSQL: pgsql/doc/src/sgml/release.sgml,v 1.332 2005/04/05 04:47:19 tgl Exp $
--> -->
<appendix id="release"> <appendix id="release">
...@@ -116,7 +116,7 @@ $PostgreSQL: pgsql/doc/src/sgml/release.sgml,v 1.331 2005/04/02 03:42:41 momjian ...@@ -116,7 +116,7 @@ $PostgreSQL: pgsql/doc/src/sgml/release.sgml,v 1.331 2005/04/02 03:42:41 momjian
<literal>CC</> and <literal>YY</> fields are both used (Karel)</para></listitem> <literal>CC</> and <literal>YY</> fields are both used (Karel)</para></listitem>
<listitem><para>Prevent <function>to_char(interval)</> from failing <listitem><para>Prevent <function>to_char(interval)</> from failing
when given a zero-month interval (Tom)</para></listitem> when given a zero-month interval (Tom)</para></listitem>
<listitem><para>Fix wrong week returned by <function>date_trunc('week')</para> <listitem><para>Fix wrong week returned by <function>date_trunc</>('week')</para>
<para> <para>
This was a problem for early January dates. <function>date_trunc('week')</> This was a problem for early January dates. <function>date_trunc('week')</>
returned the wrong year for <literal> 2005-01-01</> and <literal>2006-01-01</> returned the wrong year for <literal> 2005-01-01</> and <literal>2006-01-01</>
......
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment