|
1 | 1 | <!-- doc/src/sgml/release-8.1.sgml --> |
2 | 2 | <!-- See header comment in release.sgml about typical
8000
markup --> |
3 | 3 |
|
| 4 | + <sect1 id="release-8-1-23"> |
| 5 | + <title>Release 8.1.23</title> |
| 6 | + |
| 7 | + <note> |
| 8 | + <title>Release date</title> |
| 9 | + <simpara>2010-12-16</simpara> |
| 10 | + </note> |
| 11 | + |
| 12 | + <para> |
| 13 | + This release contains a variety of fixes from 8.1.22. |
| 14 | + For information about new features in the 8.1 major release, see |
| 15 | + <xref linkend="release-8-1">. |
| 16 | + </para> |
| 17 | + |
| 18 | + <para> |
| 19 | + This is expected to be the last <productname>PostgreSQL</> release |
| 20 | + in the 8.1.X series. Users are encouraged to update to a newer |
| 21 | + release branch soon. |
| 22 | + </para> |
| 23 | + |
| 24 | + <sect2> |
| 25 | + <title>Migration to Version 8.1.23</title> |
| 26 | + |
| 27 | + <para> |
| 28 | + A dump/restore is not required for those running 8.1.X. |
| 29 | + However, if you are upgrading from a version earlier than 8.1.18, |
| 30 | + see the release notes for 8.1.18. |
| 31 | + </para> |
| 32 | + |
| 33 | + </sect2> |
| 34 | + |
| 35 | + <sect2> |
| 36 | + <title>Changes</title> |
| 37 | + |
| 38 | + <itemizedlist> |
| 39 | + |
| 40 | + <listitem> |
| 41 | + <para> |
| 42 | + Force the default |
| 43 | + <link linkend="guc-wal-sync-method"><varname>wal_sync_method</></link> |
| 44 | + to be <literal>fdatasync</> on Linux (Tom Lane, Marti Raudsepp) |
| 45 | + </para> |
| 46 | + |
| 47 | + <para> |
| 48 | + The default on Linux has actually been <literal>fdatasync</> for many |
| 49 | + years, but recent kernel changes caused <productname>PostgreSQL</> to |
| 50 | + choose <literal>open_datasync</> instead. This choice did not result |
| 51 | + in any performance improvement, and caused outright failures on |
| 52 | + certain filesystems, notably <literal>ext4</> with the |
| 53 | + <literal>data=journal</> mount option. |
| 54 | + </para> |
| 55 | + </listitem> |
| 56 | + |
| 57 | + <listitem> |
| 58 | + <para> |
| 59 | + Fix recovery from base backup when the starting checkpoint WAL record |
| 60 | + is not in the same WAL segment as its redo point (Jeff Davis) |
| 61 | + </para> |
| 62 | + </listitem> |
| 63 | + |
| 64 | + <listitem> |
| 65 | + <para> |
| 66 | + Add support for detecting register-stack overrun on <literal>IA64</> |
| 67 | + (Tom Lane) |
| 68 | + </para> |
| 69 | + |
| 70 | + <para> |
| 71 | + The <literal>IA64</> architecture has two hardware stacks. Full |
| 72 | + prevention of stack-overrun failures requires checking both. |
| 73 | + </para> |
| 74 | + </listitem> |
| 75 | + |
| 76 | + <listitem> |
| 77 | + <para> |
| 78 | + Add a check for stack overflow in <function>copyObject()</> (Tom Lane) |
| 79 | + </para> |
| 80 | + |
| 81 | + <para> |
| 82 | + Certain code paths could crash due to stack overflow given a |
| 83 | + sufficiently complex query. |
| 84 | + </para> |
| 85 | + </listitem> |
| 86 | + |
| 87 | + <listitem> |
| 88 | + <para> |
| 89 | + Fix detection of page splits in temporary GiST indexes (Heikki |
| 90 | + Linnakangas) |
| 91 | + </para> |
| 92 | + |
| 93 | + <para> |
| 94 | + It is possible to have a <quote>concurrent</> page split in a |
| 95 | + temporary index, if for example there is an open cursor scanning the |
| 96 | + index when an insertion is done. GiST failed to detect this case and |
| 97 | + hence could deliver wrong results when execution of the cursor |
| 98 | + continued. |
| 99 | + </para> |
| 100 | + </listitem> |
| 101 | + |
| 102 | + <listitem> |
| 103 | + <para> |
| 104 | + Avoid memory leakage while <command>ANALYZE</>'ing complex index |
| 105 | + expressions (Tom Lane) |
| 106 | + </para> |
| 107 | + </listitem> |
| 108 | + |
| 109 | + <listitem> |
| 110 | + <para> |
| 111 | + Ensure an index that uses a whole-row Var still depends on its table |
| 112 | + (Tom Lane) |
| 113 | + </para> |
| 114 | + |
| 115 | + <para> |
| 116 | + An index declared like <literal>create index i on t (foo(t.*))</> |
| 117 | + would not automatically get dropped when its table was dropped. |
| 118 | + </para> |
| 119 | + </listitem> |
| 120 | + |
| 121 | + <listitem> |
| 122 | + <para> |
| 123 | + Do not <quote>inline</> a SQL function with multiple <literal>OUT</> |
| 124 | + parameters (Tom Lane) |
| 125 | + </para> |
| 126 | + |
| 127 | + <para> |
| 128 | + This avoids a possible crash due to loss of information about the |
| 129 | + expected result rowtype. |
| 130 | + </para> |
| 131 | + </listitem> |
| 132 | + |
| 133 | + <listitem> |
| 134 | + <para> |
| 135 | + Fix constant-folding of <literal>COALESCE()</> expressions (Tom Lane) |
| 136 | + </para> |
| 137 | + |
| 138 | + <para> |
| 139 | + The planner would sometimes attempt to evaluate sub-expressions that |
| 140 | + in fact could never be reached, possibly leading to unexpected errors. |
| 141 | + </para> |
| 142 | + </listitem> |
| 143 | + |
| 144 | + <listitem> |
| 145 | + <para> |
| 146 | + Add print functionality for <structname>InhRelation</> nodes (Tom Lane) |
| 147 | + </para> |
| 148 | + |
| 149 | + <para> |
| 150 | + This avoids a failure when <varname>debug_print_parse</> is enabled |
| 151 | + and certain types of query are executed. |
| 152 | + </para> |
| 153 | + </listitem> |
| 154 | + |
| 155 | + <listitem> |
| 156 | + <para> |
| 157 | + Fix incorrect calculation of distance from a point to a horizontal |
| 158 | + line segment (Tom Lane) |
| 159 | + </para> |
| 160 | + |
| 161 | + <para> |
| 162 | + This bug affected several different geometric distance-measurement |
| 163 | + operators. |
| 164 | + </para> |
| 165 | + </listitem> |
| 166 | + |
| 167 | + <listitem> |
| 168 | + <para> |
| 169 | + Fix <application>PL/pgSQL</>'s handling of <quote>simple</> |
| 170 | + expressions to not fail in recursion or error-recovery cases (Tom Lane) |
| 171 | + </para> |
| 172 | + </listitem> |
| 173 | + |
| 174 | + <listitem> |
| 175 | + <para> |
| 176 | + Fix bug in <filename>contrib/cube</>'s GiST picksplit algorithm |
| 177 | + (Alexander Korotkov) |
| 178 | + </para> |
| 179 | + |
| 180 | + <para> |
| 181 | + This could result in considerable inefficiency, though not actually |
| 182 | + incorrect answers, in a GiST index on a <type>cube</> column. |
| 183 | + If you have such an index, consider <command>REINDEX</>ing it after |
| 184 | + installing this update. |
| 185 | + </para> |
| 186 | + </listitem> |
| 187 | + |
| 188 | + <listitem> |
| 189 | + <para> |
| 190 | + Don't emit <quote>identifier will be truncated</> notices in |
| 191 | + <filename>contrib/dblink</> except when creating new connections |
| 192 | + (Itagaki Takahiro) |
| 193 | + </para> |
| 194 | + </listitem> |
| 195 | + |
| 196 | + <listitem> |
| 197 | + <para> |
| 198 | + Fix potential coredump on missing public key in |
| 199 | + <filename>contrib/pgcrypto</> (Marti Raudsepp) |
| 200 | + </para> |
| 201 | + </listitem> |
| 202 | + |
| 203 | + <listitem> |
| 204 | + <para> |
| 205 | + Fix memory leak in <filename>contrib/xml2</>'s XPath query functions |
| 206 | + (Tom Lane) |
| 207 | + </para> |
| 208 | + </listitem> |
| 209 | + |
| 210 | + <listitem> |
| 211 | + <para> |
| 212 | + Update time zone data files to <application>tzdata</> release 2010o |
| 213 | + for DST law changes in Fiji and Samoa; |
| 214 | + also historical corrections for Hong Kong. |
| 215 | + </para> |
| 216 | + </listitem> |
| 217 | + |
| 218 | + </itemizedlist> |
| 219 | + |
| 220 | + </sect2> |
| 221 | + </sect1> |
| 222 | + |
4 | 223 | <sect1 id="release-8-1-22"> |
5 | 224 | <title>Release 8.1.22</title> |
6 | 225 |
|
|
0 commit comments