|
1 | 1 | <!--
|
2 |
| -$PostgreSQL: pgsql/doc/src/sgml/release.sgml,v 1.387 2005/10/0316:04:13 tgl Exp $ |
| 2 | +$PostgreSQL: pgsql/doc/src/sgml/release.sgml,v 1.388 2005/10/0323:43:06 tgl Exp $ |
3 | 3 |
|
4 | 4 | Typical markup:
|
5 | 5 |
|
@@ -2097,6 +2097,11 @@ DATABASE</></para>
|
2097 | 2097 | <para>This should fix recent reports of <quote>index is not a btree</>
|
2098 | 2098 | failures when a crash occurs shortly after <command>CREATE
|
2099 | 2099 | DATABASE</>.</para></listitem>
|
| 2100 | +<listitem><para>Fix the sense of the test for read-only transaction |
| 2101 | +in <command>COPY</></para> |
| 2102 | +<para>The code formerly prohibited <command>COPY TO</>, where it should |
| 2103 | +prohibit <command>COPY FROM</>. |
| 2104 | +</para></listitem> |
2100 | 2105 | <listitem><para>Handle consecutive embedded newlines in <command>COPY</>
|
2101 | 2106 | CSV-mode input</para></listitem>
|
2102 | 2107 | <listitem><para>Fix <function>date_trunc(week)</> for dates near year
|
@@ -4868,6 +4873,11 @@ length when using a multiple-byte character set (Yoshiyuki Asaba)</para>
|
4868 | 4873 | <para>In prior releases, the padding of <type>CHAR()</> was incorrect
|
4869 | 4874 | because it only padded to the specified number of bytes without
|
4870 | 4875 | considering how many characters were stored.</para></listitem>
|
| 4876 | +<listitem><para>Fix the sense of the test for read-only transaction |
| 4877 | +in <command>COPY</></para> |
| 4878 | +<para>The code formerly prohibited <command>COPY TO</>, where it should |
| 4879 | +prohibit <command>COPY FROM</>. |
| 4880 | +</para></listitem> |
4871 | 4881 | <listitem><para>Fix planning problem with outer-join ON clauses that reference
|
4872 | 4882 | only the inner-side relation</para></listitem>
|
4873 | 4883 | <listitem><para>Further fixes for <literal>x FULL JOIN y ON true</> corner
|
|