|
1 | | -<!-- $PostgreSQL: pgsql/doc/src/sgml/release.sgml,v 1.576 2008/01/18 00:13:50 momjian Exp $ --> |
| 1 | +<!-- $PostgreSQL: pgsql/doc/src/sgml/release.sgml,v 1.577 2008/01/31 21:31:33 tgl Exp $ --> |
2 | 2 | <!-- |
3 | 3 |
|
4 | 4 | Typical markup: |
@@ -68,8 +68,7 @@ do it for earlier branch release files. |
68 | 68 |
|
69 | 69 | <note> |
70 | 70 | <title>Release date</title> |
71 | | - <simpara>2008-01-??</simpara> |
72 | | - <para>CURRENT AS OF 2008-01-17</> |
| 71 | + <simpara>2008-02-04</simpara> |
73 | 72 | </note> |
74 | 73 |
|
75 | 74 | <sect2> |
@@ -842,7 +841,8 @@ current_date < 2017-11-17 |
842 | 841 | middle of the table (where another sequential scan is already |
843 | 842 | in-progress) and wrapping around to the beginning to finish. This |
844 | 843 | can affect the order of returned rows in a query that does not |
845 | | - specify <literal>ORDER BY</>. |
| 844 | + specify <literal>ORDER BY</>. The <varname>synchronize_seqscans</> |
| 845 | + configuration parameter can be used to disable this if necessary. |
846 | 846 | </para> |
847 | 847 | </listitem> |
848 | 848 |
|
|