You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: doc/src/sgml/release-13.sgml
+35-30
Original file line number
Diff line number
Diff line change
@@ -87,7 +87,7 @@ Author: Tom Lane <tgl@sss.pgh.pa.us>
87
87
-->
88
88
89
89
<para>
90
-
In ltree, when using adjacent asterisks with braces, e.g. "*{2}.*{3}", properly interpret that as "*{5}" (Nikita Glukhov)
90
+
In ltree, when using adjacent asterisks with braces, e.g. ".*{2}.*{3}", properly interpret that as ".*{5}" (Nikita Glukhov)
91
91
</para>
92
92
93
93
</listitem>
@@ -273,7 +273,7 @@ Allow partitionwise joins to happen in more cases (Ashutosh Bapat, Etsuro Fujita
273
273
274
274
<para>
275
275
For example, partitionwise joins can now happen between partitioned
276
-
tables where the ancestors do not exactly match.
276
+
tables even when their partition bounds do not match exactly.
277
277
</para>
278
278
</listitem>
279
279
@@ -307,7 +307,7 @@ Allow partitioned tables to be logically replicated via publications (Amit Lango
307
307
308
308
<para>
309
309
Previously, partitions had to be replicated individually. Now partitioned tables can be published explicitly causing all partitions to be automatically published. Addition/removal of partitions from
310
-
partitioned tables are automatically added/removed from publications. The CREATE PUBLICATION option publish_via_partition_root controls whether partitioned tables are published as their own or their ancestors.
310
+
partitioned tables are automatically added/removed from publications. The CREATE PUBLICATION option publish_via_partition_root controls whether changes to partitions are published as their own or their ancestor's.
311
311
</para>
312
312
313
313
</listitem>
@@ -358,6 +358,12 @@ Author: Peter Geoghegan <pg@bowt.ie>
358
358
More efficiently store duplicates in btree indexes (Anastasia Lubennikova, Peter Geoghegan)
359
359
</para>
360
360
361
+
<para>
362
+
This allows efficient btree indexing of low cardinality columns.
363
+
Users upgrading with pg_upgrade will need to use REINDEX to make use of
364
+
this feature.
365
+
</para>
366
+
361
367
</listitem>
362
368
363
369
<listitem>
@@ -409,6 +415,12 @@ Author: Alexander Korotkov <akorotkov@postgresql.org>
409
415
Allow CREATE INDEX to specify the GiST signature length and maximum number of integer ranges (Nikita Glukhov)
410
416
</para>
411
417
418
+
<para>
419
+
Indexes created on four and eight-byte integer array, tsvector, trigram,
420
+
ltree, and hstore columns can now control these GiST index parameters,
This new behavior allows pages to be set as all-visible, which then allows index-only scans, and reduces the work necessary when the table needs to be frozen.
608
+
This new behavior reduces the work necessary when the table needs to be frozen and allows pages to be set as all-visible. All-visible pages allow index-only scans to access fewer heap rows.
0 commit comments