Movatterモバイル変換

[0]ホーム
URL:

Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

 Sign up
Appearance settings

Commit734ff84

Browse files
committed
Further wordsmithing on 9.3.3 release notes.
No substantive changes, but reorder some items and improve somedescriptions.
1 parenta5cf606 commit734ff84

File tree

1 file changed

+93
-86
lines changed

1 file changed

+93
-86
lines changed

‎doc/src/sgml/release-9.3.sgml

Lines changed: 93 additions & 86 deletions
Original file line numberDiff line numberDiff line change
@@ -70,12 +70,12 @@ Branch: REL9_3_STABLE [8e9a16ab8] 2013-12-16 11:29:51 -0300
7070
</para>
7171

7272
<para>
73-
Fixing this required changing the WALlogging format for tuple freezing.
74-
While this isunimportantfor standalone servers,in replication
75-
environments it means that <emphasis>standby servers must be upgraded
73+
Fixing this required changing the WALrecord format for tuple
74+
freezing.While this isno issuefor standalone servers,when using
75+
replication it means that <emphasis>standby servers must be upgraded
7676
to 9.3.3 or later before their masters are</>. An older standby will
77-
be unable to interpret freeze records generated by a newer master,
78-
andwill fail with a PANIC message. (In such a case, upgrading the
77+
be unable to interpret freeze records generated by a newer master, and
78+
will fail with a PANIC message. (In such a case, upgrading the
7979
standby should be sufficient to let it resume execution.)
8080
</para>
8181
</listitem>
@@ -121,16 +121,16 @@ Branch: REL9_3_STABLE [db1014bc4] 2013-12-18 13:31:27 -0300
121121
<para>
122122
If a row was locked by transaction A, and transaction B updated it,
123123
the new version of the row created by B would be locked by A, yet
124-
visible only to B.This case is new in 9.3 since prior versions did
125-
not have any types of row locking that would permit another
126-
transaction to update the row at all. If transaction B then deleted
127-
or key-updated therow, A's lock wouldn't get checked, thus possibly
128-
allowing Btocomplete when it shouldn't.
124+
visible only to B.If transaction B then again updated the row, A's
125+
lock wouldn't get checked, thus possibly allowing B to complete when
126+
it shouldn't. This case is new in 9.3 since prior versions did not
127+
have any types ofrow locking that would permit another transaction
128+
toupdate the row at all.
129129
</para>
130130

131131
<para>
132132
This oversight could allow referential integrity checks to give false
133-
positives (that is, allow deletes that should have been rejected).
133+
positives (for instance, allow deletes that should have been rejected).
134134
Applications using the new commands <literal>SELECT FOR KEY SHARE</>
135135
and <literal>SELECT FOR NO KEY UPDATE</> might also have suffered
136136
locking failures of this kind.
@@ -148,6 +148,12 @@ Branch: REL9_3_STABLE [c6cd27e36] 2013-12-05 12:21:55 -0300
148148
Prevent <quote>forgetting</> valid row locks when one of several
149149
holders of a row lock aborts (&Aacute;lvaro Herrera)
150150
</para>
151+
152+
<para>
153+
This was yet another mechanism by which a shared row lock could be
154+
lost, thus possibly allowing updates that should have been prevented
155+
by foreign-key constraints.
156+
</para>
151157
</listitem>
152158

153159
<!--
@@ -171,33 +177,33 @@ Branch: REL9_3_STABLE [2dcc48c35] 2013-12-05 17:47:51 -0300
171177

172178
<!--
173179
Author: Alvaro Herrera <alvherre@alvh.no-ip.org>
174-
Branch: master [638cf09e7] 2014-01-02 18:17:29 -0300
175-
Branch: REL9_3_STABLE [948a3dfbb] 2014-01-02 18:17:29 -0300
180+
Branch: master [a50d97625] 2014-01-02 18:17:07 -0300
181+
Branch: REL9_3_STABLE [03db79459] 2014-01-02 18:17:07 -0300
176182
-->
177183

178184
<listitem>
179185
<para>
180-
Fix handling of 5-digit filenames in <filename>pg_multixact/members</>
181-
(&Aacute;lvaro Herrera)
182-
</para>
183-
184-
<para>
185-
As of 9.3, these names can be more than 4 digits, but the directory
186-
cleanup code ignored such files.
186+
Handle wraparound correctly during extension or truncation
187+
of <filename>pg_multixact/members</>
188+
(Andres Freund, &Aacute;lvaro Herrera)
187189
</para>
188190
</listitem>
189191

190192
<!--
191193
Author: Alvaro Herrera <alvherre@alvh.no-ip.org>
192-
Branch: master [a50d97625] 2014-01-02 18:17:07 -0300
193-
Branch: REL9_3_STABLE [03db79459] 2014-01-02 18:17:07 -0300
194+
Branch: master [638cf09e7] 2014-01-02 18:17:29 -0300
195+
Branch: REL9_3_STABLE [948a3dfbb] 2014-01-02 18:17:29 -0300
194196
-->
195197

196198
<listitem>
197199
<para>
198-
Handle wraparound correctly during extension or truncation
199-
of <filename>pg_multixact/members</>
200-
(Andres Freund, &Aacute;lvaro Herrera)
200+
Fix handling of 5-digit filenames in <filename>pg_multixact/members</>
201+
(&Aacute;lvaro Herrera)
202+
</para>
203+
204+
<para>
205+
As of 9.3, these names can be more than 4 digits, but the directory
206+
cleanup code ignored such files.
201207
</para>
202208
</listitem>
203209

@@ -246,9 +252,9 @@ Branch: REL9_3_STABLE [762bd379a] 2014-02-14 15:18:34 +0200
246252
</para>
247253

248254
<para>
249-
Previously, not-yet-archived segments could get ignored during replay.
250-
This reverts an undesirable behavioral change in 9.3.0 back to the
251-
way things worked pre-9.3.
255+
Previously, not-yet-archived segments could get ignored during
256+
recovery.This reverts an undesirable behavioral change in 9.3.0
257+
back to theway things worked pre-9.3.
252258
</para>
253259
</listitem>
254260

@@ -276,7 +282,7 @@ Branch: REL8_4_STABLE [9620fede9] 2014-02-12 14:52:32 -0500
276282
applied far beyond where the end-of-file should have been. This
277283
failure mode does not appear to be a significant risk during crash
278284
recovery, only when initially synchronizing a standby created from a
279-
base backup taken froman actively-changing master.
285+
base backup taken froma quickly-changing master.
280286
</para>
281287
</listitem>
282288

@@ -298,9 +304,9 @@ Branch: REL9_0_STABLE [5301c8395] 2014-01-08 14:34:21 +0200
298304
<para>
299305
In some cases WAL replay would mistakenly conclude that the database
300306
was already consistent at the start of replay, thus possibly allowing
301-
queries before the database was really consistent. Other symptoms
302-
such as <quote>PANIC: WAL contains references to invalid pages</>
303-
were also possible.
307+
hot-standbyqueries before the database was really consistent. Other
308+
symptomssuch as <quote>PANIC: WAL contains references to invalid
309+
pages</>were also possible.
304310
</para>
305311
</listitem>
306312

@@ -328,7 +334,7 @@ Branch: REL9_0_STABLE [5d742b9ce] 2014-01-14 17:35:00 -0500
328334
<listitem>
329335
<para>
330336
Fix improper locking of btree index pages while replaying
331-
a <literal>VACUUM</> operation inHot Standby mode (Andres Freund,
337+
a <literal>VACUUM</> operation inhot-standby mode (Andres Freund,
332338
Heikki Linnakangas, Tom Lane)
333339
</para>
334340

@@ -350,13 +356,13 @@ Branch: REL8_4_STABLE [67fc33d3a] 2013-12-03 22:53:26 +0200
350356

351357
<listitem>
352358
<para>
353-
Ensure that insertions into non-leaf GIN index pagesmake a full-page
359+
Ensure that insertions into non-leaf GIN index pageswrite a full-page
354360
WAL record when appropriate (Heikki Linnakangas)
355361
</para>
356362

357363
<para>
358-
The previous coding riskeddata corruption in the event of a
359-
torn-pageupdate.
364+
The previous coding riskedindex corruption in the event of a
365+
partial-pagewrite during a system crash.
360366
</para>
361367
</listitem>
362368

@@ -385,7 +391,7 @@ Branch: REL9_3_STABLE [e34acac62] 2014-01-16 23:14:57 +0200
385391

386392
<listitem>
387393
<para>
388-
Ensure walreceiver sendsHot Standby feedback messages on time even
394+
Ensure walreceiver sendshot-standby feedback messages on time even
389395
when there is a continuous stream of data (Andres Freund, Amit
390396
Kapila)
391397
</para>
@@ -461,7 +467,7 @@ Branch: REL8_4_STABLE [01b882fd8] 2014-01-29 20:04:14 -0500
461467

462468
<listitem>
463469
<para>
464-
Fix unsafe references to <varname>errno</> within errormessaging
470+
Fix unsafe references to <varname>errno</> within errorreporting
465471
logic (Christian Kruse)
466472
</para>
467473

@@ -505,13 +511,13 @@ Branch: REL8_4_STABLE [7635dae55] 2013-12-05 12:48:44 -0500
505511

506512
<listitem>
507513
<para>
508-
Clear retry flags properly inreplacementOpenSSL socket write
514+
Clear retry flags properly in OpenSSL socket write
509515
function (Alexander Kukushkin)
510516
</para>
511517

512518
<para>
513-
This omissionresultedin a server lockup after unexpected loss of an
514-
SSL-encrypted connection.
519+
This omissioncould resultin a server lockup after unexpected loss
520+
of anSSL-encrypted connection.
515521
</para>
516522
</listitem>
517523

@@ -695,7 +701,7 @@ Branch: REL8_4_STABLE [00b77771a] 2014-01-11 13:42:11 -0500
695701

696702
<para>
697703
<command>ANALYZE</> intentionally omits very wide values from its
698-
histogram and most-common-value calculations, but it neglected to do
704+
histogram and most-common-values calculations, but it neglected to do
699705
something sane in the case that all the sampled entries are too wide.
700706
</para>
701707
</listitem>
@@ -718,8 +724,8 @@ Branch: REL8_4_STABLE [0fb4e3ceb] 2014-01-18 18:50:47 -0500
718724
</para>
719725

720726
<para>
721-
<literal>CREATE TABLE</>works this way, but <literal>ALTER TABLE</>
722-
didn't get the memo.
727+
<literal>CREATE TABLE</>has always allowed such usage,
728+
but <literal>ALTER TABLE</>didn't get the memo.
723729
</para>
724730
</listitem>
725731

@@ -747,8 +753,8 @@ Branch: REL8_4_STABLE [57ac7d8a7] 2014-01-08 20:18:24 -0500
747753

748754
<listitem>
749755
<para>
750-
Fix <quote>cannot accept a set</> error when some arms of a CASE
751-
return a set and others don't (Tom Lane)
756+
Fix <quote>cannot accept a set</> error when some arms of
757+
a <literal>CASE</>return a set and others don't (Tom Lane)
752758
</para>
753759
</listitem>
754760

@@ -873,7 +879,7 @@ Branch: REL8_4_STABLE [69f77d756] 2013-12-15 11:11:11 +0900
873879
<listitem>
874880
<para>
875881
Accept <literal>SHIFT_JIS</> as an encoding name for locale checking
876-
(Tatsuo Ishii)
882+
purposes(Tatsuo Ishii)
877883
</para>
878884
</listitem>
879885

@@ -929,7 +935,7 @@ Branch: REL8_4_STABLE [7644a7bd8] 2014-02-13 18:45:32 -0500
929935

930936
<listitem>
931937
<para>
932-
Improve error handling in <application>psql</> and <application>libpq</>
938+
Improve error handling in <application>libpq</> and <application>psql</>
933939
for failures during <literal>COPY TO STDOUT/FROM STDIN</> (Tom Lane)
934940
</para>
935941

@@ -959,21 +965,6 @@ Branch: REL9_2_STABLE [fa28f9cba] 2014-01-04 16:05:23 -0500
959965
</para>
960966
</listitem>
961967

962-
<!--
963-
Author: Magnus Hagander <magnus@hagander.net>
964-
Branch: master [b168c5ef2] 2014-01-07 17:11:32 +0100
965-
Branch: REL9_3_STABLE [0463b9419] 2014-01-07 17:11:51 +0100
966-
Branch: REL9_2_STABLE [2edf3e82c] 2014-01-07 17:22:36 +0100
967-
Branch: REL9_1_STABLE [773e4d5e4] 2014-01-07 17:18:02 +0100
968-
-->
969-
970-
<listitem>
971-
<para>
972-
Avoid including tablespaces inside PGDATA twice in base backups
973-
(Dimitri Fontaine, Magnus Hagander)
974-
</para>
975-
</listitem>
976-
977968
<!--
978969
Author: Magnus Hagander <magnus@hagander.net>
979970
Branch: master [63ab2befe] 2014-02-12 18:45:18 +0100
@@ -1003,6 +994,21 @@ Branch: REL9_1_STABLE [c6e5c4dd1] 2014-02-09 12:09:55 +0100
1003994
</para>
1004995
</listitem>
1005996

997+
<!--
998+
Author: Magnus Hagander <magnus@hagander.net>
999+
Branch: master [b168c5ef2] 2014-01-07 17:11:32 +0100
1000+
Branch: REL9_3_STABLE [0463b9419] 2014-01-07 17:11:51 +0100
1001+
Branch: REL9_2_STABLE [2edf3e82c] 2014-01-07 17:22:36 +0100
1002+
Branch: REL9_1_STABLE [773e4d5e4] 2014-01-07 17:18:02 +0100
1003+
-->
1004+
1005+
<listitem>
1006+
<para>
1007+
Avoid including tablespaces inside PGDATA twice in base backups
1008+
(Dimitri Fontaine, Magnus Hagander)
1009+
</para>
1010+
</listitem>
1011+
10061012
<!--
10071013
Author: Michael Meskes <meskes@postgresql.org>
10081014
Branch: master [d685e2424] 2014-01-09 16:20:19 +0100
@@ -1049,7 +1055,7 @@ Branch: REL8_4_STABLE [6c8b16e30] 2013-12-07 16:56:34 -0800
10491055
<listitem>
10501056
<para>
10511057
Fix performance regression in <filename>contrib/dblink</> connection
1052-
setup (Joe Conway)
1058+
startup (Joe Conway)
10531059
</para>
10541060

10551061
<para>
@@ -1132,22 +1138,6 @@ Branch: REL8_4_STABLE [15699d9bf] 2014-01-17 23:17:59 -0500
11321138
</para>
11331139
</listitem>
11341140

1135-
<!--
1136-
Author: Andrew Dunstan <andrew@dunslane.net>
1137-
Branch: master [7e1531a45] 2014-02-01 16:08:33 -0500
1138-
Branch: REL9_3_STABLE [27942baf4] 2014-02-01 16:13:32 -0500
1139-
Branch: REL9_2_STABLE [fad443753] 2014-02-01 16:13:46 -0500
1140-
Branch: REL9_1_STABLE [e5c22c15d] 2014-02-01 16:14:01 -0500
1141-
Branch: REL9_0_STABLE [1c0bf372f] 2014-02-01 16:14:15 -0500
1142-
-->
1143-
1144-
<listitem>
1145-
<para>
1146-
Avoid using the deprecated <literal>dllwrap</> tool in Cygwin builds
1147-
(Marco Atzeri)
1148-
</para>
1149-
</listitem>
1150-
11511141
<!--
11521142
Author: Andrew Dunstan <andrew@dunslane.net>
11531143
Branch: master [d587298b8] 2014-02-01 15:11:13 -0500
@@ -1171,6 +1161,22 @@ Branch: REL8_4_STABLE [ae3c98b9b] 2014-02-01 15:16:52 -0500
11711161
</para>
11721162
</listitem>
11731163

1164+
<!--
1165+
Author: Andrew Dunstan <andrew@dunslane.net>
1166+
Branch: master [7e1531a45] 2014-02-01 16:08:33 -0500
1167+
Branch: REL9_3_STABLE [27942baf4] 2014-02-01 16:13:32 -0500
1168+
Branch: REL9_2_STABLE [fad443753] 2014-02-01 16:13:46 -0500
1169+
Branch: REL9_1_STABLE [e5c22c15d] 2014-02-01 16:14:01 -0500
1170+
Branch: REL9_0_STABLE [1c0bf372f] 2014-02-01 16:14:15 -0500
1171+
-->
1172+
1173+
<listitem>
1174+
<para>
1175+
Avoid using the deprecated <literal>dllwrap</> tool in Cygwin builds
1176+
(Marco Atzeri)
1177+
</para>
1178+
</listitem>
1179+
11741180
<!--
11751181
Author: Andrew Dunstan <andrew@dunslane.net>
11761182
Branch: master [cec8394b5] 2014-01-26 09:49:10 -0500
@@ -1202,11 +1208,11 @@ Branch: REL8_4_STABLE [432735cbf] 2014-02-10 20:48:30 -0500
12021208
<para>
12031209
These text files duplicated the main HTML and PDF documentation
12041210
formats. The trouble involved in maintaining them greatly outweighs
1205-
the likely audience forthis format. Distribution tarballs will
1206-
still contain files by these names, but they'll just be stubs
1211+
the likely audience forplain-text format. Distribution tarballs
1212+
willstill contain files by these names, but they'll just be stubs
12071213
directing the reader to consult the main documentation.
12081214
The plain-text <filename>INSTALL</> file will still be maintained, as
1209-
there is arguablyan audience for that.
1215+
there is arguablya use-case for that.
12101216
</para>
12111217
</listitem>
12121218

@@ -1227,9 +1233,10 @@ Branch: REL8_4_STABLE [c0c2d62ac] 2014-02-14 21:59:56 -0500
12271233
</para>
12281234

12291235
<para>
1230-
In addition, the zones Asia/Riyadh87, Asia/Riyadh88, and
1231-
Asia/Riyadh89 have been removed, as they are no longer maintained by
1232-
IANA, and never represented actual civil timekeeping practice.
1236+
In addition, the zones <literal>Asia/Riyadh87</>,
1237+
<literal>Asia/Riyadh88</>, and <literal>Asia/Riyadh89</> have been
1238+
removed, as they are no longer maintained by IANA, and never
1239+
represented actual civil timekeeping practice.
12331240
</para>
12341241
</listitem>
12351242

0 commit comments

Comments
 (0)
[8]ページ先頭
©2009-2025 Movatter.jp