@@ -87,7 +87,7 @@ Author: Tom Lane <tgl@sss.pgh.pa.us>
...
@@ -87,7 +87,7 @@ Author: Tom Lane <tgl@sss.pgh.pa.us>
-->
-->
<para>
<para>
In ltree, when using adjacent asterisks with braces, e.g. "*{2}.*{3}", properly interpret that as "*{5}" (Nikita Glukhov)
In ltree, when using adjacent asterisks with braces, e.g. ".*{2}.*{3}", properly interpret that as ".*{5}" (Nikita Glukhov)
</para>
</para>
</listitem>
</listitem>
...
@@ -273,7 +273,7 @@ Allow partitionwise joins to happen in more cases (Ashutosh Bapat, Etsuro Fujita
...
@@ -273,7 +273,7 @@ Allow partitionwise joins to happen in more cases (Ashutosh Bapat, Etsuro Fujita
<para>
<para>
For example, partitionwise joins can now happen between partitioned
For example, partitionwise joins can now happen between partitioned
tables where the ancestors do not exactly match.
tables even when their partition bounds do not match exactly.
</para>
</para>
</listitem>
</listitem>
...
@@ -307,7 +307,7 @@ Allow partitioned tables to be logically replicated via publications (Amit Lango
...
@@ -307,7 +307,7 @@ Allow partitioned tables to be logically replicated via publications (Amit Lango
<para>
<para>
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
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
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.
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.
</para>
</para>
</listitem>
</listitem>
...
@@ -358,6 +358,12 @@ Author: Peter Geoghegan <pg@bowt.ie>
...
@@ -358,6 +358,12 @@ Author: Peter Geoghegan <pg@bowt.ie>
More efficiently store duplicates in btree indexes (Anastasia Lubennikova, Peter Geoghegan)
More efficiently store duplicates in btree indexes (Anastasia Lubennikova, Peter Geoghegan)
</para>
</para>
<para>
This allows efficient btree indexing of low cardinality columns.
Users upgrading with pg_upgrade will need to use REINDEX to make use of
this feature.
</para>
</listitem>
</listitem>
<listitem>
<listitem>
...
@@ -409,6 +415,12 @@ Author: Alexander Korotkov <akorotkov@postgresql.org>
...
@@ -409,6 +415,12 @@ Author: Alexander Korotkov <akorotkov@postgresql.org>
Allow CREATE INDEX to specify the GiST signature length and maximum number of integer ranges (Nikita Glukhov)
Allow CREATE INDEX to specify the GiST signature length and maximum number of integer ranges (Nikita Glukhov)
</para>
</para>
<para>
Indexes created on four and eight-byte integer array, tsvector, trigram,
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.
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.