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

Commit6eb612f

Browse files
committed
doc: update PG 11 release notes
Discussion:https://postgr.es/m/1f5b2e66-7ba8-98ec-c06a-aee9ff33f050@postgresql.orgAuthor: Jonathan S. KatzBackpatch-through: 11
1 parentc87cb5f commit6eb612f

File tree

1 file changed

+33
-26
lines changed

1 file changed

+33
-26
lines changed

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

Lines changed: 33 additions & 26 deletions
Original file line numberDiff line numberDiff line change
@@ -6,7 +6,7 @@
66

77
<formalpara>
88
<title>Release date:</title>
9-
<para>2018-??-?? (CURRENT AS OF 2018-07-30)</para>
9+
<para>2018-10-?? (CURRENT AS OF 2018-09-20)</para>
1010
</formalpara>
1111

1212
<sect2>
@@ -22,7 +22,7 @@
2222

2323
<listitem>
2424
<para>
25-
Major improvementsto partitioning:
25+
Improvementsto partitioning functionality, including:
2626
<itemizedlist>
2727
<listitem>
2828
<para>
@@ -37,9 +37,8 @@
3737
</listitem>
3838
<listitem>
3939
<para>
40-
Improved <command>SELECT</command> query performance due to
41-
enhanced partition elimination during query processing and
42-
execution
40+
Improved <command>SELECT</command> performance from enhanced partition
41+
elimination strategies during query processing and execution
4342
</para>
4443
</listitem>
4544
<listitem>
@@ -48,29 +47,37 @@
4847
KEY</literal>, indexes, and triggers on partitioned tables
4948
</para>
5049
</listitem>
50+
<listitem>
51+
<para>
52+
Having a "default" partition for storing data that does not match any
53+
of the remaining partitions
54+
</para>
55+
</listitem>
5156
</itemizedlist>
5257
</para>
5358
</listitem>
5459

5560
<listitem>
5661
<para>
57-
Improvements to parallelism:
62+
Improvements to parallelism, including:
5863
<itemizedlist>
5964
<listitem>
6065
<para>
61-
Parallelized hash joins
66+
B-tree indexes can now be built in parallel with
67+
<command>CREATE INDEX</command>
6268
</para>
6369
</listitem>
6470
<listitem>
6571
<para>
66-
Parallelized <command>CREATE INDEX</command> for B-tree indexes
72+
Parallelized <command>CREATE TABLE .. AS</command>,
73+
<command>CREATE MATERIALIZED VIEW</command>, and certain
74+
queries using <literal>UNION</literal>
6775
</para>
6876
</listitem>
6977
<listitem>
7078
<para>
71-
Parallelized <command>CREATE TABLE .. AS</command>,
72-
<command>CREATE MATERIALIZED VIEW</command>, and certain
73-
queries using <literal>UNION</literal>
79+
Performance improvements for parallelized hash joins and parallelized
80+
sequential scans
7481
</para>
7582
</listitem>
7683
</itemizedlist>
@@ -79,7 +86,10 @@
7986

8087
<listitem>
8188
<para>
82-
SQL stored procedures, with support for embedded transactions
89+
SQL stored procedures that support embedded transactions. Stored
90+
procedures can be created with <link linkend="sql-createprocedure">
91+
<command>CREATE PROCEDURE</command></link> and executed with
92+
<link linkend="sql-call"><command>CALL</command></link>
8393
</para>
8494
</listitem>
8595

@@ -99,6 +109,13 @@
99109
</para>
100110
</listitem>
101111

112+
<listitem>
113+
<para>
114+
Covering indexes, which can be utilized using the
115+
<literal>INCLUDE</literal> clause of <command>CREATE INDEX</command>
116+
</para>
117+
</listitem>
118+
102119
<listitem>
103120
<para>
104121
Many other useful performance improvements, including making
@@ -179,10 +196,6 @@
179196
would be dumped without such specifications if the database locale
180197
and encoding matched the old cluster's defaults.
181198
</para>
182-
183-
<para>
184-
DID I GET EVERYTHING?
185-
</para>
186199
</listitem>
187200

188201
<listitem>
@@ -597,8 +610,7 @@
597610
The new command <link linkend="sql-alterindex"><command>ALTER
598611
INDEX ATTACH PARTITION</command></link> allows indexes to be
599612
attached to partitions. This does not behave as a global index
600-
since the contents are private to each index. WARN WHEN USING
601-
AN EXISTING INDEX?
613+
since the contents are private to each index.
602614
</para>
603615
</listitem>
604616

@@ -907,7 +919,7 @@ same commits as above
907919
</para>
908920

909921
<para>
910-
This reduces the likelihood of serialization conflicts. ACCURATE?
922+
This reduces the likelihood of serialization conflicts.
911923
</para>
912924
</listitem>
913925

@@ -1980,7 +1992,6 @@ same commits as above
19801992
<command>CALL</command>s or in nested PL/pgSQL DO and
19811993
<command>CALL</command> blocks that only contain other PL/pgSQL
19821994
<command>DO</command> and <command>CALL</command> blocks.
1983-
ACCURATE?
19841995
</para>
19851996
</listitem>
19861997

@@ -2405,11 +2416,6 @@ same commits as above
24052416
when the <acronym>WAL</acronym> streaming method
24062417
(<option>--wal-method=stream</option>) is used.
24072418
</para>
2408-
2409-
<para>
2410-
IS IT CLEAR FROM THE DOCS THAT THE REPLICATION SLOT IS NOT
2411-
TEMPORARY?
2412-
</para>
24132419
</listitem>
24142420

24152421
<listitem>
@@ -2904,7 +2910,8 @@ same commits as above
29042910
</para>
29052911

29062912
<para>
2907-
This is useful for KNN-GiST searches. HOW?
2913+
This is useful for KNN-GiST searches when looking for coordinates in
2914+
descending order.
29082915
</para>
29092916
</listitem>
29102917

0 commit comments

Comments
 (0)

[8]ページ先頭

©2009-2025 Movatter.jp