/
release-9.4.sgml
11811 lines (10575 loc) · 473 KB
/
release-9.4.sgml
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372
373
374
375
376
377
378
379
380
381
382
383
384
385
386
387
388
389
390
391
392
393
394
395
396
397
398
399
400
401
402
403
404
405
406
407
408
409
410
411
412
413
414
415
416
417
418
419
420
421
422
423
424
425
426
427
428
429
430
431
432
433
434
435
436
437
438
439
440
441
442
443
444
445
446
447
448
449
450
451
452
453
454
455
456
457
458
459
460
461
462
463
464
465
466
467
468
469
470
471
472
473
474
475
476
477
478
479
480
481
482
483
484
485
486
487
488
489
490
491
492
493
494
495
496
497
498
499
500
501
502
503
504
505
506
507
508
509
510
511
512
513
514
515
516
517
518
519
520
521
522
523
524
525
526
527
528
529
530
531
532
533
534
535
536
537
538
539
540
541
542
543
544
545
546
547
548
549
550
551
552
553
554
555
556
557
558
559
560
561
562
563
564
565
566
567
568
569
570
571
572
573
574
575
576
577
578
579
580
581
582
583
584
585
586
587
588
589
590
591
592
593
594
595
596
597
598
599
600
601
602
603
604
605
606
607
608
609
610
611
612
613
614
615
616
617
618
619
620
621
622
623
624
625
626
627
628
629
630
631
632
633
634
635
636
637
638
639
640
641
642
643
644
645
646
647
648
649
650
651
652
653
654
655
656
657
658
659
660
661
662
663
664
665
666
667
668
669
670
671
672
673
674
675
676
677
678
679
680
681
682
683
684
685
686
687
688
689
690
691
692
693
694
695
696
697
698
699
700
701
702
703
704
705
706
707
708
709
710
711
712
713
714
715
716
717
718
719
720
721
722
723
724
725
726
727
728
729
730
731
732
733
734
735
736
737
738
739
740
741
742
743
744
745
746
747
748
749
750
751
752
753
754
755
756
757
758
759
760
761
762
763
764
765
766
767
768
769
770
771
772
773
774
775
776
777
778
779
780
781
782
783
784
785
786
787
788
789
790
791
792
793
794
795
796
797
798
799
800
801
802
803
804
805
806
807
808
809
810
811
812
813
814
815
816
817
818
819
820
821
822
823
824
825
826
827
828
829
830
831
832
833
834
835
836
837
838
839
840
841
842
843
844
845
846
847
848
849
850
851
852
853
854
855
856
857
858
859
860
861
862
863
864
865
866
867
868
869
870
871
872
873
874
875
876
877
878
879
880
881
882
883
884
885
886
887
888
889
890
891
892
893
894
895
896
897
898
899
900
901
902
903
904
905
906
907
908
909
910
911
912
913
914
915
916
917
918
919
920
921
922
923
924
925
926
927
928
929
930
931
932
933
934
935
936
937
938
939
940
941
942
943
944
945
946
947
948
949
950
951
952
953
954
955
956
957
958
959
960
961
962
963
964
965
966
967
968
969
970
971
972
973
974
975
976
977
978
979
980
981
982
983
984
985
986
987
988
989
990
991
992
993
994
995
996
997
998
999
1000
<!-- doc/src/sgml/release-9.4.sgml -->
<!-- See header comment in release.sgml about typical markup -->
<sect1 id="release-9-4-9">
<!--==========================orignal english content==========================
<title>Release 9.4.9</title>
____________________________________________________________________________-->
<title>版本 9.4.9</title>
<note>
<!--==========================orignal english content==========================
<title>Release Date</title>
____________________________________________________________________________-->
<title>发布日期</title>
<!--==========================orignal english content==========================
<simpara>2016-08-11</simpara>
____________________________________________________________________________-->
<simpara>2016-08-11</simpara>
</note>
<!--==========================orignal english content==========================
<para>
This release contains a variety of fixes from 9.4.8.
For information about new features in the 9.4 major release, see
<xref linkend="release-9-4">.
</para>
____________________________________________________________________________-->
<para>
这个版本包含各种自9.4.8以来的修复。
关于9.4主版本的新特性信息,请查看
<xref linkend="release-9-4">。
</para>
<sect2>
<!--==========================orignal english content==========================
<title>Migration to Version 9.4.9</title>
____________________________________________________________________________-->
<title>迁移到版本 9.4.9</title>
<!--==========================orignal english content==========================
<para>
A dump/restore is not required for those running 9.4.X.
</para>
____________________________________________________________________________-->
<para>
运行9.4.X版本的用户不需要转储/恢复。
</para>
<!--==========================orignal english content==========================
<para>
However, if you are upgrading from a version earlier than 9.4.6,
see <xref linkend="release-9-4-6">.
</para>
____________________________________________________________________________-->
<para>
不过,如果您是从一个早于9.4.6的版本升级而来,那么请查看
<xref linkend="release-9-4-6">。
</para>
</sect2>
<sect2>
<!--==========================orignal english content==========================
<title>Changes</title>
____________________________________________________________________________-->
<title>修改列表</title>
<itemizedlist>
<listitem>
<!--==========================orignal english content==========================
<para>
Fix possible mis-evaluation of
nested <literal>CASE</>-<literal>WHEN</> expressions (Heikki
Linnakangas, Michael Paquier, Tom Lane)
</para>
____________________________________________________________________________-->
<para>
修复嵌套的<literal>CASE</>-<literal>WHEN</>表达式可能的错误估算 (Heikki
Linnakangas, Michael Paquier, Tom Lane)
</para>
<!--==========================orignal english content==========================
<para>
A <literal>CASE</> expression appearing within the test value
subexpression of another <literal>CASE</> could become confused about
whether its own test value was null or not. Also, inlining of a SQL
function implementing the equality operator used by
a <literal>CASE</> expression could result in passing the wrong test
value to functions called within a <literal>CASE</> expression in the
SQL function's body. If the test values were of different data
types, a crash might result; moreover such situations could be abused
to allow disclosure of portions of server memory. (CVE-2016-5423)
</para>
____________________________________________________________________________-->
<para>
出现在另一个<literal>CASE</>的测试值子表达式中的<literal>CASE</>
表达式可能会困惑自己的测试值是否为空。此外,
<literal>CASE</>表达式使用的实现等式运算符的SQL函数的内联,
可能会导致将错误的测试值传递给在SQL函数体内的<literal>CASE</>
表达式中调用的函数。如果测试值是不同的数据类型,可能会导致崩溃;
此外,这种情况可能被滥用以允许披露服务器存储器的一部分。 (CVE-2016-5423)
</para>
</listitem>
<listitem>
<!--==========================orignal english content==========================
<para>
Fix client programs' handling of special characters in database and
role names (Noah Misch, Nathan Bossart, Michael Paquier)
</para>
____________________________________________________________________________-->
<para>
修复客户端程序在数据库和角色名称中对特殊字符的处理
(Noah Misch, Nathan Bossart, Michael Paquier)
</para>
<!--==========================orignal english content==========================
<para>
Numerous places in <application>vacuumdb</> and other client programs
could become confused by database and role names containing double
quotes or backslashes. Tighten up quoting rules to make that safe.
Also, ensure that when a conninfo string is used as a database name
parameter to these programs, it is correctly treated as such throughout.
</para>
____________________________________________________________________________-->
<para>
<application>vacuumdb</>
和其他客户端程序中的许多地方可能会被包含双引号或反斜杠的数据库和角色名称混淆。
加强引用规则以使其是安全的。此外,确保将conninfo字符串用作这些程序的数据库名称参数时,
它将被正确地对待。
</para>
<!--==========================orignal english content==========================
<para>
Fix handling of paired double quotes
in <application>psql</>'s <command>\connect</>
and <command>\password</> commands to match the documentation.
</para>
____________________________________________________________________________-->
<para>
修正在<application>psql</>的<command>\connect</>和<command>\password</>
命令中配对双引号的处理,以匹配文档。
</para>
<!--==========================orignal english content==========================
<para>
Introduce a new <option>-reuse-previous</> option
in <application>psql</>'s <command>\connect</> command to allow
explicit control of whether to re-use connection parameters from a
previous connection. (Without this, the choice is based on whether
the database name looks like a conninfo string, as before.) This
allows secure handling of database names containing special
characters in <application>pg_dumpall</> scripts.
</para>
____________________________________________________________________________-->
<para>
在<application>psql</>的<command>\connect</>命令中引入一个新的
<option>-reuse-previous</>选项,以允许显式控制是否重新使用先前连接的连接参数。
(没有这个选择是基于数据库名称是否像以前一样是conninfo字符串。)
这允许在<application>pg_dumpall</>脚本中安全处理包含特殊字符的数据库名称。
</para>
<!--==========================orignal english content==========================
<para>
<application>pg_dumpall</> now refuses to deal with database and role
names containing carriage returns or newlines, as it seems impractical
to quote those characters safely on Windows. In future we may reject
such names on the server side, but that step has not been taken yet.
</para>
____________________________________________________________________________-->
<para>
<application>pg_dumpall</>现在拒绝处理包含回车或换行的数据库或角色名,
因为在Windows上安全的引用这些字符似乎是不切实际的。
将来我们可能在服务器端拒绝这样的名称,但是现在还未采取这一步骤。
</para>
<!--==========================orignal english content==========================
<para>
These are considered security fixes because crafted object names
containing special characters could have been used to execute
commands with superuser privileges the next time a superuser
executes <application>pg_dumpall</> or other routine maintenance
operations. (CVE-2016-5424)
</para>
____________________________________________________________________________-->
<para>
这些被认为是安全修复程序,
因为包含特殊字符的制作对象名称可能已被用于在下次超级用户执行
<application>pg_dumpall</>或其他例行维护操作时执行具有超级用户权限的命令。
(CVE-2016-5424)
</para>
</listitem>
<listitem>
<!--==========================orignal english content==========================
<para>
Fix corner-case misbehaviors for <literal>IS NULL</>/<literal>IS NOT
NULL</> applied to nested composite values (Andrew Gierth, Tom Lane)
</para>
____________________________________________________________________________-->
<para>
修复针对<literal>IS NULL</>/<literal>IS NOT
NULL</>应用于嵌套复合值的极端情况错误行为 (Andrew Gierth, Tom Lane)
</para>
<!--==========================orignal english content==========================
<para>
The SQL standard specifies that <literal>IS NULL</> should return
TRUE for a row of all null values (thus <literal>ROW(NULL,NULL) IS
NULL</> yields TRUE), but this is not meant to apply recursively
(thus <literal>ROW(NULL, ROW(NULL,NULL)) IS NULL</> yields FALSE).
The core executor got this right, but certain planner optimizations
treated the test as recursive (thus producing TRUE in both cases),
and <filename>contrib/postgres_fdw</> could produce remote queries
that misbehaved similarly.
</para>
____________________________________________________________________________-->
<para>
SQL标准指定<literal>IS NULL</>应该为所有空值的行返回TRUE(因此
<literal>ROW(NULL,NULL) IS NULL</>产生TRUE),但这并不意味着应用递归
(因此<literal>ROW(NULL, ROW(NULL,NULL)) IS NULL</>产生FALSE)。
内核执行器正确执行了,但某些计划器优化将测试视为递归
(因此在这两种情况下都会产生TRUE),并且<filename>contrib/postgres_fdw</>
可能会产生类似错误的远程查询。
</para>
</listitem>
<listitem>
<!--==========================orignal english content==========================
<para>
Make the <type>inet</> and <type>cidr</> data types properly reject
IPv6 addresses with too many colon-separated fields (Tom Lane)
</para>
____________________________________________________________________________-->
<para>
使<type>inet</>和<type>cidr</>
数据类型正确拒绝具有太多冒号分隔字段的IPv6地址 (Tom Lane)
</para>
</listitem>
<listitem>
<!--==========================orignal english content==========================
<para>
Prevent crash in <function>close_ps()</>
(the <type>point</> <literal>##</> <type>lseg</> operator)
for NaN input coordinates (Tom Lane)
</para>
____________________________________________________________________________-->
<para>
防止NaN输入坐标的<function>close_ps()</>中的崩溃
(<type>point</> <literal>##</> <type>lseg</>操作符)
(Tom Lane)
</para>
<!--==========================orignal english content==========================
<para>
Make it return NULL instead of crashing.
</para>
____________________________________________________________________________-->
<para>
使其返回NULL而不是崩溃。
</para>
</listitem>
<listitem>
<!--==========================orignal english content==========================
<para>
Avoid possible crash in <function>pg_get_expr()</> when inconsistent
values are passed to it (Michael Paquier, Thomas Munro)
</para>
____________________________________________________________________________-->
<para>
避免在<function>pg_get_expr()</>中传递不一致的值时发生崩溃
(Michael Paquier, Thomas Munro)
</para>
</listitem>
<listitem>
<!--==========================orignal english content==========================
<para>
Fix several one-byte buffer over-reads in <function>to_number()</>
(Peter Eisentraut)
</para>
____________________________________________________________________________-->
<para>
修复<function>to_number()</>中的几个单字节缓冲区溢出
(Peter Eisentraut)
</para>
<!--==========================orignal english content==========================
<para>
In several cases the <function>to_number()</> function would read one
more character than it should from the input string. There is a
small chance of a crash, if the input happens to be adjacent to the
end of memory.
</para>
____________________________________________________________________________-->
<para>
在某些情况下<function>to_number()</>函数将从输入字符串中多读取一个字符。
如果输入恰好与内存的结束相邻,那么会有可能崩溃。
</para>
</listitem>
<listitem>
<!--==========================orignal english content==========================
<para>
Do not run the planner on the query contained in <literal>CREATE
MATERIALIZED VIEW</> or <literal>CREATE TABLE AS</>
when <literal>WITH NO DATA</> is specified (Michael Paquier,
Tom Lane)
</para>
____________________________________________________________________________-->
<para>
当指定了<literal>WITH NO DATA</>时,不要在包含在<literal>CREATE
MATERIALIZED VIEW</>或<literal>CREATE TABLE AS</>
中的查询上运行规划器 (Michael Paquier,
Tom Lane)
</para>
<!--==========================orignal english content==========================
<para>
This avoids some unnecessary failure conditions, for example if a
stable function invoked by the materialized view depends on a table
that doesn't exist yet.
</para>
____________________________________________________________________________-->
<para>
这避免了一些不必要的失败条件,例如,如果物化视图调用的稳定函数依赖于尚不存在的表。
</para>
</listitem>
<listitem>
<!--==========================orignal english content==========================
<para>
Avoid unsafe intermediate state during expensive paths
through <function>heap_update()</> (Masahiko Sawada, Andres Freund)
</para>
____________________________________________________________________________-->
<para>
通过<function>heap_update()</>在昂贵的路径中避免不安全的中间状态
(Masahiko Sawada, Andres Freund)
</para>
<!--==========================orignal english content==========================
<para>
Previously, these cases locked the target tuple (by setting its XMAX)
but did not WAL-log that action, thus risking data integrity problems
if the page were spilled to disk and then a database crash occurred
before the tuple update could be completed.
</para>
____________________________________________________________________________-->
<para>
以前,这些情况锁定了目标元组(通过设置其XMAX),但没有WAL-log这个操作,
因此如果页面溢出到磁盘,然后在元组更新完成之前发生数据库崩溃,
就会有数据完整性问题的风险。
</para>
</listitem>
<listitem>
<!--==========================orignal english content==========================
<para>
Fix hint bit update during WAL replay of row locking operations
(Andres Freund)
</para>
____________________________________________________________________________-->
<para>
在行锁定操作的WAL重放期间修正提示位更新
(Andres Freund)
</para>
<!--==========================orignal english content==========================
<para>
The only known consequence of this problem is that row locks held by
a prepared, but uncommitted, transaction might fail to be enforced
after a crash and restart.
</para>
____________________________________________________________________________-->
<para>
这个问题的唯一已知后果是,由准备但未提交的事务持有的行锁在崩溃和重新启动后可能无法执行。
</para>
</listitem>
<listitem>
<!--==========================orignal english content==========================
<para>
Avoid unnecessary <quote>could not serialize access</> errors when
acquiring <literal>FOR KEY SHARE</> row locks in serializable mode
(Álvaro Herrera)
</para>
____________________________________________________________________________-->
<para>
当在序列化模式中请求<literal>FOR KEY SHARE</>行锁时,
避免不必要的<quote>could not serialize access</>错误
(Álvaro Herrera)
</para>
</listitem>
<listitem>
<!--==========================orignal english content==========================
<para>
Avoid crash in <literal>postgres -C</> when the specified variable
has a null string value (Michael Paquier)
</para>
____________________________________________________________________________-->
<para>
当指定的变量具有空字符串值时,避免在<literal>postgres -C</>中崩溃
(Michael Paquier)
</para>
</listitem>
<listitem>
<!--==========================orignal english content==========================
<para>
Fix possible loss of large subtransactions in logical decoding
(Petru-Florin Mihancea)
</para>
____________________________________________________________________________-->
<para>
修复逻辑解码中可能的大量子事务丢失
(Petru-Florin Mihancea)
</para>
</listitem>
<listitem>
<!--==========================orignal english content==========================
<para>
Fix failure of logical decoding when a subtransaction contains no
actual changes (Marko Tiikkaja, Andrew Gierth)
</para>
____________________________________________________________________________-->
<para>
当子事务不包含实际修改时,修复逻辑解码失败 (Marko Tiikkaja, Andrew Gierth)
</para>
</listitem>
<listitem>
<!--==========================orignal english content==========================
<para>
Ensure that backends see up-to-date statistics for shared catalogs
(Tom Lane)
</para>
____________________________________________________________________________-->
<para>
确保后端查看共享目录的最新统计信息
(Tom Lane)
</para>
<!--==========================orignal english content==========================
<para>
The statistics collector failed to update the statistics file for
shared catalogs after a request from a regular backend. This problem
was partially masked because the autovacuum launcher regularly makes
requests that did cause such updates; however, it became obvious with
autovacuum disabled.
</para>
____________________________________________________________________________-->
<para>
在普通后端的请求后,统计信息收集器无法更新共享目录的统计信息文件。
这个问题被部分掩盖了,因为自动清理启动器定期发出导致这种更新的请求;
然而,禁用自动清理后变得明显。
</para>
</listitem>
<listitem>
<!--==========================orignal english content==========================
<para>
Avoid redundant writes of the statistics files when multiple
backends request updates close together (Tom Lane, Tomas Vondra)
</para>
____________________________________________________________________________-->
<para>
当多个后端请求更新时,请避免对统计文件进行冗余写入 (Tom Lane, Tomas Vondra)
</para>
</listitem>
<listitem>
<!--==========================orignal english content==========================
<para>
Avoid consuming a transaction ID during <command>VACUUM</>
(Alexander Korotkov)
</para>
____________________________________________________________________________-->
<para>
避免在<command>VACUUM</>期间使用事务ID
(Alexander Korotkov)
</para>
<!--==========================orignal english content==========================
<para>
Some cases in <command>VACUUM</> unnecessarily caused an XID to be
assigned to the current transaction. Normally this is negligible,
but if one is up against the XID wraparound limit, consuming more
XIDs during anti-wraparound vacuums is a very bad thing.
</para>
____________________________________________________________________________-->
<para>
<command>VACUUM</>中的某些情况不必要地导致将XID分配给当前事务。
通常这是可以忽略不计的,但如果是针对XID环绕限制,
在反包装清理中消耗更多的XID是一件非常糟糕的事情。
</para>
</listitem>
<listitem>
<!--==========================orignal english content==========================
<para>
Avoid canceling hot-standby queries during <command>VACUUM FREEZE</>
(Simon Riggs, Álvaro Herrera)
</para>
____________________________________________________________________________-->
<para>
避免在<command>VACUUM FREEZE</>期间取消热备用查询
(Simon Riggs, Álvaro Herrera)
</para>
<!--==========================orignal english content==========================
<para>
<command>VACUUM FREEZE</> on an otherwise-idle master server could
result in unnecessary cancellations of queries on its standby
servers.
</para>
____________________________________________________________________________-->
<para>
在空闲的主服务器上的<command>VACUUM FREEZE</>
可能导致在其备用服务器上不必要地取消查询。
</para>
</listitem>
<listitem>
<!--==========================orignal english content==========================
<para>
Prevent possible failure when vacuuming multixact IDs in an
installation that has been pg_upgrade'd from pre-9.3 (Andrew Gierth,
Álvaro Herrera)
</para>
____________________________________________________________________________-->
<para>
在从9.3之前pg_upgrade的安装中清理多重ID时,防止可能的失败
(Andrew Gierth,Álvaro Herrera)
</para>
<!--==========================orignal english content==========================
<para>
The usual symptom of this bug is errors
like <quote>MultiXactId <replaceable>NNN</> has not been created
yet -− apparent wraparound</quote>.
</para>
____________________________________________________________________________-->
<para>
这个bug的常见情况是像<quote>MultiXactId <replaceable>NNN</> has not been created
yet -- apparent wraparound</quote>这样的错误。
</para>
</listitem>
<listitem>
<!--==========================orignal english content==========================
<para>
When a manual <command>ANALYZE</> specifies a column list, don't
reset the table's <literal>changes_since_analyze</> counter
(Tom Lane)
</para>
____________________________________________________________________________-->
<para>
当手动<command>ANALYZE</>指定列列表时,请不要重置表的
<literal>changes_since_analyze</>计数器 (Tom Lane)
</para>
<!--==========================orignal english content==========================
<para>
If we're only analyzing some columns, we should not prevent routine
auto-analyze from happening for the other columns.
</para>
____________________________________________________________________________-->
<para>
如果我们只是分析一些列,我们不应该阻止对其他列的日常自动分析。
</para>
</listitem>
<listitem>
<!--==========================orignal english content==========================
<para>
Fix <command>ANALYZE</>'s overestimation of <literal>n_distinct</>
for a unique or nearly-unique column with many null entries (Tom
Lane)
</para>
____________________________________________________________________________-->
<para>
修复<command>ANALYZE</>对具有许多空条目的唯一或几乎唯一的列进行过高估计
<literal>n_distinct</> (Tom Lane)
</para>
<!--==========================orignal english content==========================
<para>
The nulls could get counted as though they were themselves distinct
values, leading to serious planner misestimates in some types of
queries.
</para>
____________________________________________________________________________-->
<para>
空值可以被计数就像它们本身是不同的值,导致在某些类型的查询中严重的规划器错误估计。
</para>
</listitem>
<listitem>
<!--==========================orignal english content==========================
<para>
Prevent autovacuum from starting multiple workers for the same shared
catalog (Álvaro Herrera)
</para>
____________________________________________________________________________-->
<para>
防止autovacuum启动为同一个共享目录的多个工作进程 (Álvaro Herrera)
</para>
<!--==========================orignal english content==========================
<para>
Normally this isn't much of a problem because the vacuum doesn't take
long anyway; but in the case of a severely bloated catalog, it could
result in all but one worker uselessly waiting instead of doing
useful work on other tables.
</para>
____________________________________________________________________________-->
<para>
通常这不是很大的问题,因为清理不需要很长时间;但是在目录严重膨胀的情况下,
除了一个工作进程外,所有工作进程都将无用地等待,而不是在其他表格上进行有用的工作。
</para>
</listitem>
<listitem>
<!--==========================orignal english content==========================
<para>
Avoid duplicate buffer lock release when abandoning a b-tree index
page deletion attempt (Tom Lane)
</para>
____________________________________________________________________________-->
<para>
在放弃b-tree索引页删除尝试时避免重复的缓冲区锁释放 (Tom Lane)
</para>
<!--==========================orignal english content==========================
<para>
This mistake prevented <command>VACUUM</> from completing in some
cases involving corrupt b-tree indexes.
</para>
____________________________________________________________________________-->
<para>
在某些情况下,包括损坏的b-tree索引,这种错误阻止了<command>VACUUM</>完成。
</para>
</listitem>
<listitem>
<!--==========================orignal english content==========================
<para>
Prevent infinite loop in GiST index build for geometric columns
containing NaN component values (Tom Lane)
</para>
____________________________________________________________________________-->
<para>
阻止GiST索引构建中包含NaN组件值的几何列的无限循环 (Tom Lane)
</para>
</listitem>
<listitem>
<!--==========================orignal english content==========================
<para>
Fix <filename>contrib/btree_gin</> to handle the smallest
possible <type>bigint</> value correctly (Peter Eisentraut)
</para>
____________________________________________________________________________-->
<para>
修复<filename>contrib/btree_gin</>,以正确处理最小可能的
<type>bigint</>值 (Peter Eisentraut)
</para>
</listitem>
<listitem>
<!--==========================orignal english content==========================
<para>
Teach libpq to correctly decode server version from future servers
(Peter Eisentraut)
</para>
____________________________________________________________________________-->
<para>
教会libpq正确解码未来服务器的服务器版本
(Peter Eisentraut)
</para>
<!--==========================orignal english content==========================
<para>
It's planned to switch to two-part instead of three-part server
version numbers for releases after 9.6. Make sure
that <function>PQserverVersion()</> returns the correct value for
such cases.
</para>
____________________________________________________________________________-->
<para>
计划在9.6之后的版本切换到两部分而不是三部分服务器版本号。确保
<function>PQserverVersion()</>为这种情况返回正确的值。
</para>
</listitem>
<listitem>
<!--==========================orignal english content==========================
<para>
Fix <application>ecpg</>'s code for <literal>unsigned long long</>
array elements (Michael Meskes)
</para>
____________________________________________________________________________-->
<para>
修复<application>ecpg</>为<literal>unsigned long long</>
数组元素的编码 (Michael Meskes)
</para>
</listitem>
<listitem>
<!--==========================orignal english content==========================
<para>
In <application>pg_dump</> with both <option>-c</> and <option>-C</>
options, avoid emitting an unwanted <literal>CREATE SCHEMA public</>
command (David Johnston, Tom Lane)
</para>
____________________________________________________________________________-->
<para>
在同时具有<option>-c</>和<option>-C</>选项的<application>pg_dump</>中,
避免发出不需要的<literal>CREATE SCHEMA public</>命令 (David Johnston, Tom Lane)
</para>
</listitem>
<listitem>
<!--==========================orignal english content==========================
<para>
Improve handling of <systemitem>SIGTERM</>/control-C in
parallel <application>pg_dump</> and <application>pg_restore</> (Tom
Lane)
</para>
____________________________________________________________________________-->
<para>
改进并行<application>pg_dump</>和<application>pg_restore</>
中<systemitem>SIGTERM</>/control-C的处理 (Tom
Lane)
</para>
<!--==========================orignal english content==========================
<para>
Make sure that the worker processes will exit promptly, and also arrange
to send query-cancel requests to the connected backends, in case they
are doing something long-running such as a <command>CREATE INDEX</>.
</para>
____________________________________________________________________________-->
<para>
确保工作进程将立即退出,并且还安排向所连接的后端发送查询取消请求,
以防万一他们正在进行长时间的运行,例如<command>CREATE INDEX</>。
</para>
</listitem>
<listitem>
<!--==========================orignal english content==========================
<para>
Fix error reporting in parallel <application>pg_dump</>
and <application>pg_restore</> (Tom Lane)
</para>
____________________________________________________________________________-->
<para>
修复并行<application>pg_dump</>和<application>pg_restore</>
中的错误报告 (Tom Lane)
</para>
<!--==========================orignal english content==========================
<para>
Previously, errors reported by <application>pg_dump</>
or <application>pg_restore</> worker processes might never make it to
the user's console, because the messages went through the master
process, and there were various deadlock scenarios that would prevent
the master process from passing on the messages. Instead, just print
everything to <literal>stderr</>. In some cases this will result in
duplicate messages (for instance, if all the workers report a server
shutdown), but that seems better than no message.
</para>
____________________________________________________________________________-->
<para>
以前,<application>pg_dump</>或<application>pg_restore</>
工作进程报告的错误可能永远不会发送给用户的控制台,因为消息通过主进程,
并且有各种死锁情况会阻止主进程传递消息。相反,只需打印一切到
<literal>stderr</>。 在某些情况下,这将导致重复的消息(例如,
如果所有的工作进程都报告服务器关闭),但这似乎比没有消息更好。
</para>
</listitem>
<listitem>
<!--==========================orignal english content==========================
<para>
Ensure that parallel <application>pg_dump</>
or <application>pg_restore</> on Windows will shut down properly
after an error (Kyotaro Horiguchi)
</para>
____________________________________________________________________________-->
<para>
确保Windows上并行的<application>pg_dump</>或
<application>pg_restore</>在错误后正确关闭 (Kyotaro Horiguchi)
</para>
<!--==========================orignal english content==========================
<para>
Previously, it would report the error, but then just sit until
manually stopped by the user.
</para>
____________________________________________________________________________-->
<para>
以前,它会报告错误,但是之后会等待直到用户手动停止。
</para>
</listitem>
<listitem>
<!--==========================orignal english content==========================
<para>
Make <application>pg_dump</> behave better when built without zlib
support (Kyotaro Horiguchi)
</para>
____________________________________________________________________________-->
<para>
在不使用zlib支持的情况下,使<application>pg_dump</>的行为更好
(Kyotaro Horiguchi)
</para>
<!--==========================orignal english content==========================
<para>
It didn't work right for parallel dumps, and emitted some rather
pointless warnings in other cases.
</para>
____________________________________________________________________________-->
<para>
它并不适用于并行转储,并在其他情况下发出了一些相当无意义的警告。
</para>
</listitem>
<listitem>
<!--==========================orignal english content==========================
<para>
Make <application>pg_basebackup</> accept <literal>-Z 0</> as
specifying no compression (Fujii Masao)
</para>
____________________________________________________________________________-->
<para>
让<application>pg_basebackup</>接受<literal>-Z 0</>
指定不压缩 (Fujii Masao)
</para>
</listitem>
<listitem>
<!--==========================orignal english content==========================
<para>
Fix makefiles' rule for building AIX shared libraries to be safe for
parallel make (Noah Misch)
</para>
____________________________________________________________________________-->
<para>
修复用于构建AIX共享库的makefile文件规则对于并行make是安全的 (Noah Misch)
</para>
</listitem>
<listitem>
<!--==========================orignal english content==========================
<para>
Fix TAP tests and MSVC scripts to work when build directory's path
name contains spaces (Michael Paquier, Kyotaro Horiguchi)
</para>
____________________________________________________________________________-->
<para>
修复TAP测试和MSVC脚本使其在构建目录的路径名中包含空格时可以运行
(Michael Paquier, Kyotaro Horiguchi)
</para>
</listitem>
<listitem>
<!--==========================orignal english content==========================
<para>
Be more predictable about reporting <quote>statement timeout</>
versus <quote>lock timeout</> (Tom Lane)
</para>
____________________________________________________________________________-->
<para>
针对<quote>锁定超时</>报告<quote>语句超时</>
更加可预测 (Tom Lane)
</para>
<!--==========================orignal english content==========================
<para>
On heavily loaded machines, the regression tests sometimes failed due
to reporting <quote>lock timeout</> even though the statement timeout
should have occurred first.
</para>
____________________________________________________________________________-->
<para>
在负载较重的机器上,即使应该已经先发生了语句超时,
因为报告<quote>锁定超时</>,回归测试有时也会失败。
</para>
</listitem>
<listitem>
<!--==========================orignal english content==========================
<para>
Make regression tests safe for Danish and Welsh locales (Jeff Janes,
Tom Lane)
</para>
____________________________________________________________________________-->
<para>
使回归测试对丹麦和威尔士环境是安全的 (Jeff Janes,
Tom Lane)
</para>
<!--==========================orignal english content==========================
<para>
Change some test data that triggered the unusual sorting rules of
these locales.
</para>
____________________________________________________________________________-->
<para>
更改一些触发这些区域设置的异常排序规则的测试数据。
</para>
</listitem>
<listitem>
<!--==========================orignal english content==========================
<para>
Update our copy of the timezone code to match
IANA's <application>tzcode</> release 2016c (Tom Lane)
</para>
____________________________________________________________________________-->
<para>
更新或拷贝时区代码以匹配IANA的<application>tzcode</>版本2016c (Tom Lane)
</para>
<!--==========================orignal english content==========================
<para>
This is needed to cope with anticipated future changes in the time
zone data files. It also fixes some corner-case bugs in coping with
unusual time zones.
</para>
____________________________________________________________________________-->
<para>
这需要应对时区数据文件中预期的未来变化。它还修复了一些处理异常时区的角落错误。
</para>
</listitem>
<listitem>
<!--==========================orignal english content==========================
<para>
Update time zone data files to <application>tzdata</> release 2016f
for DST law changes in Kemerovo and Novosibirsk, plus historical
corrections for Azerbaijan, Belarus, and Morocco.
</para>
____________________________________________________________________________-->
<para>
将时区数据文件更新为Kemerovo和新西伯利亚的DST法律变更的
<application>tzdata</>版本2016f,以及阿塞拜疆、白俄罗斯和摩洛哥的历史更正。
</para>
</listitem>
</itemizedlist>
</sect2>
</sect1>
<sect1 id="release-9-4-8">
<!--==========================orignal english content==========================
<title>Release 9.4.8</title>
____________________________________________________________________________-->
<title>版本 9.4.8</title>
<note>
<!--==========================orignal english content==========================
<title>Release Date</title>
____________________________________________________________________________-->
<title>发布日期</title>
<!--==========================orignal english content==========================
<simpara>2016-05-12</simpara>
____________________________________________________________________________-->
<simpara>2016-05-12</simpara>
</note>
<!--==========================orignal english content==========================
<para>
This release contains a variety of fixes from 9.4.7.
For information about new features in the 9.4 major release, see
<xref linkend="release-9-4">.
</para>
____________________________________________________________________________-->
<para>
这个版本包含各种自9.4.7以来的修复。关于9.4主版本的新特性信息,
请查看<xref linkend="release-9-4">。
</para>
<sect2>
<!--==========================orignal english content==========================
<title>Migration to Version 9.4.8</title>
____________________________________________________________________________-->
<title>迁移到版本 9.4.8</title>
<!--==========================orignal english content==========================
<para>
A dump/restore is not required for those running 9.4.X.