PG 10 release notes

On 04/25/2017 03:31 AM, Bruce Momjian wrote:

I have committed the first draft of the Postgres 10 release notes. They
are current as of two days ago, and I will keep them current. Please
give me any feedback you have.

This item is incorrectly attributed to me. I was only the reviewer,
Peter is the author.

+<listitem>
+<!--
+Author: Peter Eisentraut <peter_e@gmx.net>
+2016-12-20 [1753b1b02] Add pg_sequence system catalog
+-->
+<para>
+Create a <link 
linkend="catalog-pg-sequence"><structname>pg_sequence</></> system 
catalog to store sequence metadata (Andreas
+Karlsson)
+</para>

Andreas

--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers

On Tue, Apr 25, 2017 at 03:45:52AM +0200, Andreas Karlsson wrote:

On 04/25/2017 03:31 AM, Bruce Momjian wrote:

I have committed the first draft of the Postgres 10 release notes. They
are current as of two days ago, and I will keep them current. Please
give me any feedback you have.

This item is incorrectly attributed to me. I was only the reviewer, Peter is
the author.

+<listitem>
+<!--
+Author: Peter Eisentraut <peter_e@gmx.net>
+2016-12-20 [1753b1b02] Add pg_sequence system catalog
+-->
+<para>
+Create a <link linkend="catalog-pg-sequence"><structname>pg_sequence</></>
system catalog to store sequence metadata (Andreas
+Karlsson)
+</para>

OK, fixed. I also moved some "incompatibility" items into the right
section. FYI, you can see the most recent doc build here:

http://momjian.us/pgsql_docs/release-10.html

--
Bruce Momjian <bruce@momjian.us> http://momjian.us
EnterpriseDB http://enterprisedb.com

+ As you are, so once was I.  As I am, so you will be. +
+                      Ancient Roman grave inscription +

--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers

Hello, Bruce

From: pgsql-hackers-owner@postgresql.org
[mailto:pgsql-hackers-owner@postgresql.org] On Behalf Of Bruce Momjian
I have committed the first draft of the Postgres 10 release notes. They
are current as of two days ago, and I will keep them current. Please give
me any feedback you have.

Thanks for a nice release note. Below is what I noticed:

(1)
Support parallel bitmap heap scans (Dilip Kum)

This item appears twice.

(2)
E.1.3.1.4. Optimizer
Remove SCO and Unixware ports (Tom Lane)

The section doesn't seem appropriate. Is OS-specific code related to the optimizer?

(3)
Remove documented restriction about using large shared buffers on Windows (Tsunakawa, Takayuki)

Please change the name to "Takayuki Tsunakawa".

(4)
Have to_timestamp() and to_date() check check input values for validity (Artur Zakirov)

"check" is repeated.

(5)
Use POSIX semaphores rather than SysV semaphores on Linux and FreeBSD (Tom Lane)
This avoids some limits on SysV semaphores usage.

These two lines are put in two different items.

Regards
Takayuki Tsunakawa

--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers

All fixed, thanks.

---------------------------------------------------------------------------

On Tue, Apr 25, 2017 at 02:40:23AM +0000, Tsunakawa, Takayuki wrote:

Hello, Bruce

From: pgsql-hackers-owner@postgresql.org
[mailto:pgsql-hackers-owner@postgresql.org] On Behalf Of Bruce Momjian
I have committed the first draft of the Postgres 10 release notes. They
are current as of two days ago, and I will keep them current. Please give
me any feedback you have.

Thanks for a nice release note. Below is what I noticed:

(1)
Support parallel bitmap heap scans (Dilip Kum)

This item appears twice.

(2)
E.1.3.1.4. Optimizer
Remove SCO and Unixware ports (Tom Lane)

The section doesn't seem appropriate. Is OS-specific code related to the optimizer?

(3)
Remove documented restriction about using large shared buffers on Windows (Tsunakawa, Takayuki)

Please change the name to "Takayuki Tsunakawa".

(4)
Have to_timestamp() and to_date() check check input values for validity (Artur Zakirov)

"check" is repeated.

(5)
Use POSIX semaphores rather than SysV semaphores on Linux and FreeBSD (Tom Lane)
This avoids some limits on SysV semaphores usage.

These two lines are put in two different items.

Regards
Takayuki Tsunakawa

--
Bruce Momjian <bruce@momjian.us> http://momjian.us
EnterpriseDB http://enterprisedb.com

+ As you are, so once was I.  As I am, so you will be. +
+                      Ancient Roman grave inscription +

--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers

On Tue, Apr 25, 2017 at 7:01 AM, Bruce Momjian <bruce@momjian.us> wrote:

I have committed the first draft of the Postgres 10 release notes. They
are current as of two days ago, and I will keep them current. Please
give me any feedback you have.

Some of the items which I feel could be added:

5e6d8d2bbbcace304450b309e79366c0da4063e4
Allow parallel workers to execute subplans.

61c2e1a95f94bb904953a6281ce17a18ac38ee6d
Improve access to parallel query from procedural languages.

In Parallel Queries section, we can add above two items as they
increase the usage of the parallel query in many cases.

ea69a0dead5128c421140dc53fac165ba4af8520
Expand hash indexes more gradually.

I think the above commit needs a separate mention, as this is a really
huge step forward to control the size of hash indexes.

--
With Regards,
Amit Kapila.
EnterpriseDB: http://www.enterprisedb.com

--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers

On Tue, Apr 25, 2017 at 08:30:50AM +0530, Amit Kapila wrote:

On Tue, Apr 25, 2017 at 7:01 AM, Bruce Momjian <bruce@momjian.us> wrote:

I have committed the first draft of the Postgres 10 release notes. They
are current as of two days ago, and I will keep them current. Please
give me any feedback you have.

Some of the items which I feel could be added:

5e6d8d2bbbcace304450b309e79366c0da4063e4
Allow parallel workers to execute subplans.

Uh, can you show me the commit on that and give some text ideas?

61c2e1a95f94bb904953a6281ce17a18ac38ee6d
Improve access to parallel query from procedural languages.

I think I have that:

Increase parallel query usage in procedural language functions (Robert
Haas)

In Parallel Queries section, we can add above two items as they
increase the usage of the parallel query in many cases.

ea69a0dead5128c421140dc53fac165ba4af8520
Expand hash indexes more gradually.

That is in this item:

Improve hash bucket split performance by reducing locking requirements
(Amit Kapila, Mithun Cy)

Also cache hash index meta-information for faster lookups. Additional
hash performance improvements have also been made. pg_upgrade'd hash
indexes from previous major Postgres versions must be rebuilt.

Can you suggest additional wording? I did merge many of the hash items
into this so it would be understandable. You can see the commits in the
SGML source.

I think the above commit needs a separate mention, as this is a really
huge step forward to control the size of hash indexes.

Yes, it is unfotunate that the item is in the incompatibility item. I
wonder if I should split out the need to rebuild the hash indexes and
keep it there and move this item into the "Index" section.

--
Bruce Momjian <bruce@momjian.us> http://momjian.us
EnterpriseDB http://enterprisedb.com

+ As you are, so once was I.  As I am, so you will be. +
+                      Ancient Roman grave inscription +

--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers

On Tue, Apr 25, 2017 at 8:30 AM, Amit Kapila <amit.kapila16@gmail.com> wrote:

On Tue, Apr 25, 2017 at 7:01 AM, Bruce Momjian <bruce@momjian.us> wrote:

I have committed the first draft of the Postgres 10 release notes. They
are current as of two days ago, and I will keep them current. Please
give me any feedback you have.

Some of the items which I feel could be added:

5e6d8d2bbbcace304450b309e79366c0da4063e4
Allow parallel workers to execute subplans.

61c2e1a95f94bb904953a6281ce17a18ac38ee6d
Improve access to parallel query from procedural languages.

In Parallel Queries section, we can add above two items as they
increase the usage of the parallel query in many cases.

I see the second one in release notes, but maybe we should credit
Rafia Sabih as well for that feature as she was the original author of
the patch and has helped in fixing the bugs that occurred due to that
feature.

--
With Regards,
Amit Kapila.
EnterpriseDB: http://www.enterprisedb.com

--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers

On Tue, Apr 25, 2017 at 08:36:38AM +0530, Amit Kapila wrote:

On Tue, Apr 25, 2017 at 8:30 AM, Amit Kapila <amit.kapila16@gmail.com> wrote:

On Tue, Apr 25, 2017 at 7:01 AM, Bruce Momjian <bruce@momjian.us> wrote:

I have committed the first draft of the Postgres 10 release notes. They
are current as of two days ago, and I will keep them current. Please
give me any feedback you have.

Some of the items which I feel could be added:

5e6d8d2bbbcace304450b309e79366c0da4063e4
Allow parallel workers to execute subplans.

61c2e1a95f94bb904953a6281ce17a18ac38ee6d
Improve access to parallel query from procedural languages.

In Parallel Queries section, we can add above two items as they
increase the usage of the parallel query in many cases.

I see the second one in release notes, but maybe we should credit
Rafia Sabih as well for that feature as she was the original author of
the patch and has helped in fixing the bugs that occurred due to that
feature.

Added.

--
Bruce Momjian <bruce@momjian.us> http://momjian.us
EnterpriseDB http://enterprisedb.com

+ As you are, so once was I.  As I am, so you will be. +
+                      Ancient Roman grave inscription +

--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers

On Mon, Apr 24, 2017 at 11:05:41PM -0400, Bruce Momjian wrote:

I think the above commit needs a separate mention, as this is a really
huge step forward to control the size of hash indexes.

Yes, it is unfotunate that the item is in the incompatibility item. I
wonder if I should split out the need to rebuild the hash indexes and
keep it there and move this item into the "Index" section.

Done, items split.

--
Bruce Momjian <bruce@momjian.us> http://momjian.us
EnterpriseDB http://enterprisedb.com

+ As you are, so once was I.  As I am, so you will be. +
+                      Ancient Roman grave inscription +

--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers

On Tue, Apr 25, 2017 at 8:35 AM, Bruce Momjian <bruce@momjian.us> wrote:

On Tue, Apr 25, 2017 at 08:30:50AM +0530, Amit Kapila wrote:

On Tue, Apr 25, 2017 at 7:01 AM, Bruce Momjian <bruce@momjian.us> wrote:

I have committed the first draft of the Postgres 10 release notes. They
are current as of two days ago, and I will keep them current. Please
give me any feedback you have.

Some of the items which I feel could be added:

5e6d8d2bbbcace304450b309e79366c0da4063e4
Allow parallel workers to execute subplans.

Uh, can you show me the commit on that and give some text ideas?

I have already mentioned the commit id (5e6d8d2b). Text can be "Allow
queries containing subplans to execute in parallel". We should also
mention in some way that this applies only when the query contains
uncorrelated subplan.

61c2e1a95f94bb904953a6281ce17a18ac38ee6d
Improve access to parallel query from procedural languages.

I think I have that:

Increase parallel query usage in procedural language functions (Robert
Haas)

In Parallel Queries section, we can add above two items as they
increase the usage of the parallel query in many cases.

ea69a0dead5128c421140dc53fac165ba4af8520
Expand hash indexes more gradually.

That is in this item:

Improve hash bucket split performance by reducing locking requirements
(Amit Kapila, Mithun Cy)

Also cache hash index meta-information for faster lookups. Additional
hash performance improvements have also been made. pg_upgrade'd hash
indexes from previous major Postgres versions must be rebuilt.

Can you suggest additional wording?

Allow hash indexes to expand slowly

This will help in controlling the size of hash indexes after the split.

I did merge many of the hash items
into this so it would be understandable. You can see the commits in the
SGML source.

I think the above commit needs a separate mention, as this is a really
huge step forward to control the size of hash indexes.

Yes, it is unfotunate that the item is in the incompatibility item. I
wonder if I should split out the need to rebuild the hash indexes and
keep it there and move this item into the "Index" section.

That sounds sensible.

--
With Regards,
Amit Kapila.
EnterpriseDB: http://www.enterprisedb.com

--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers

On 2017-04-24 21:31:44 -0400, Bruce Momjian wrote:

I have committed the first draft of the Postgres 10 release notes. They
are current as of two days ago, and I will keep them current. Please
give me any feedback you have.

The only unusual thing is that this release has ~180 items while most
recent release have had ~220. The pattern I see that there are more
large features in this release than previous ones.

I think that might also be because you skipped a few things that should
get their own entries. I've not yet made a pass through your draft (and
won't for some days), but a quick search shows the draft to e.g miss:
b30d3ea824c5ccba43d3e942704f20686e7dbab8 - Add a macro templatized hashtable.
75ae538bc3168bf44475240d4e0487ee2f3bb376 - Use more efficient hashtable for tidbitmap.c to speed up bitmap scans.
5dfc198146b49ce7ecc8a1fc9d5e171fb75f6ba5 - Use more efficient hashtable for execGrouping.c to speed up hash aggregation.
fc4b3dea2950e4f6081f1ed2380f82c9efd672e0 - User narrower representative tuples in the hash-agg hashtable.
8ed3f11bb045ad7a3607690be668dbd5b3cc31d7 - Perform one only projection to compute agg arguments.
(not that this needs to five entries)

- Andres

--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers

On Mon, Apr 24, 2017 at 08:36:00PM -0700, Andres Freund wrote:

On 2017-04-24 21:31:44 -0400, Bruce Momjian wrote:

I have committed the first draft of the Postgres 10 release notes. They
are current as of two days ago, and I will keep them current. Please
give me any feedback you have.

The only unusual thing is that this release has ~180 items while most
recent release have had ~220. The pattern I see that there are more
large features in this release than previous ones.

I think that might also be because you skipped a few things that should
get their own entries. I've not yet made a pass through your draft (and
won't for some days), but a quick search shows the draft to e.g miss:
b30d3ea824c5ccba43d3e942704f20686e7dbab8 - Add a macro templatized hashtable.
75ae538bc3168bf44475240d4e0487ee2f3bb376 - Use more efficient hashtable for tidbitmap.c to speed up bitmap scans.
5dfc198146b49ce7ecc8a1fc9d5e171fb75f6ba5 - Use more efficient hashtable for execGrouping.c to speed up hash aggregation.
fc4b3dea2950e4f6081f1ed2380f82c9efd672e0 - User narrower representative tuples in the hash-agg hashtable.
8ed3f11bb045ad7a3607690be668dbd5b3cc31d7 - Perform one only projection to compute agg arguments.
(not that this needs to five entries)

I remember seeing those and those are normally details I do not put in
the release notes as there isn't a clear user experience change except
"Postgres is faster". Yeah, a bummer, and I can change my filter, but
it would require discussion.

--
Bruce Momjian <bruce@momjian.us> http://momjian.us
EnterpriseDB http://enterprisedb.com

+ As you are, so once was I.  As I am, so you will be. +
+                      Ancient Roman grave inscription +

--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers

On 2017-04-24 23:37:42 -0400, Bruce Momjian wrote:

On Mon, Apr 24, 2017 at 08:36:00PM -0700, Andres Freund wrote:

On 2017-04-24 21:31:44 -0400, Bruce Momjian wrote:

I have committed the first draft of the Postgres 10 release notes. They
are current as of two days ago, and I will keep them current. Please
give me any feedback you have.

The only unusual thing is that this release has ~180 items while most
recent release have had ~220. The pattern I see that there are more
large features in this release than previous ones.

I think that might also be because you skipped a few things that should
get their own entries. I've not yet made a pass through your draft (and
won't for some days), but a quick search shows the draft to e.g miss:
b30d3ea824c5ccba43d3e942704f20686e7dbab8 - Add a macro templatized hashtable.
75ae538bc3168bf44475240d4e0487ee2f3bb376 - Use more efficient hashtable for tidbitmap.c to speed up bitmap scans.
5dfc198146b49ce7ecc8a1fc9d5e171fb75f6ba5 - Use more efficient hashtable for execGrouping.c to speed up hash aggregation.
fc4b3dea2950e4f6081f1ed2380f82c9efd672e0 - User narrower representative tuples in the hash-agg hashtable.
8ed3f11bb045ad7a3607690be668dbd5b3cc31d7 - Perform one only projection to compute agg arguments.
(not that this needs to five entries)

I remember seeing those and those are normally details I do not put in
the release notes as there isn't a clear user experience change except
"Postgres is faster". Yeah, a bummer, and I can change my filter, but
it would require discussion.

I think "postgres is faster" is one of the bigger user demands, so I
don't think that policy makes much sense. A large number of the changes
over the next few releases will focus solely on that. Nor do I think
past release notes particularly filtered such changes out.

- Andres

--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers

Andres Freund <andres@anarazel.de> writes:

On 2017-04-24 23:37:42 -0400, Bruce Momjian wrote:

I remember seeing those and those are normally details I do not put in
the release notes as there isn't a clear user experience change except
"Postgres is faster". Yeah, a bummer, and I can change my filter, but
it would require discussion.

I think "postgres is faster" is one of the bigger user demands, so I
don't think that policy makes much sense. A large number of the changes
over the next few releases will focus solely on that. Nor do I think
past release notes particularly filtered such changes out.

I think it has been pretty common to accumulate a lot of such changes
into generic entries like, say, "speedups for hash joins". More detail
than that simply isn't useful to end users; and as a rule, our release
notes are too long anyway.

regards, tom lane

--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers

On 2017-04-24 23:45:06 -0400, Tom Lane wrote:

Andres Freund <andres@anarazel.de> writes:

On 2017-04-24 23:37:42 -0400, Bruce Momjian wrote:

I remember seeing those and those are normally details I do not put in
the release notes as there isn't a clear user experience change except
"Postgres is faster". Yeah, a bummer, and I can change my filter, but
it would require discussion.

I think "postgres is faster" is one of the bigger user demands, so I
don't think that policy makes much sense. A large number of the changes
over the next few releases will focus solely on that. Nor do I think
past release notes particularly filtered such changes out.

I think it has been pretty common to accumulate a lot of such changes
into generic entries like, say, "speedups for hash joins". More detail
than that simply isn't useful to end users; and as a rule, our release
notes are too long anyway.

Oh, I completely agree with accumulating related changes, and that
code-level details aren't useful. I think we skipped them entirely
here. And I just listed my own changes because I could find them
quickly, but they're not alone, e.g:
090010f2ec9b1f9ac1124dc628b89586f911b641 - Improve performance of find_tabstat_entry()/get_tabstat_entry()
which makes it realistic to have sessions touching many relations, which
previously was O(#relations^2), and which caused repeated complaints
over the years, and allows for different usecases.

- Andres

--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers

Hi,

I wonder if there's a reasonable way that allows to add links to the
more crucial commits for changelog entries. The source e.g. has

<listitem>
<!--
Author: Robert Haas <rhaas@postgresql.org>
2017-03-08 [98e6e8904] tidbitmap: Support shared iteration.
Author: Robert Haas <rhaas@postgresql.org>
2017-03-08 [f35742ccb] Support parallel bitmap heap scans.
-->
<para>
Support parallel bitmap heap scans (Dilip Kumar)
</para>

<para>
This allows a single index scan to dispatch parallel workers to process
different areas of the heap.
</para>
</listitem>

for an item, and it'd be pretty cool if we could have a link to those
two commits from the entry. It'd need be pretty unobstrusive to avoid
making things hard to read, but it'd obviate some of the need to list
details, and it gives curious people changes to see what actually
changed.

- Andres

--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers

..On 25 April 2017 at 13:31, Bruce Momjian <bruce@momjian.us> wrote:

The only unusual thing is that this release has ~180 items while most
recent release have had ~220. The pattern I see that there are more
large features in this release than previous ones.

Thanks for drafting this up.

I understand that it may have been filtered out, but I'd say that
7e534adcdc70 is worth a mention.

Users creating BRIN indexes previously would have had to know
beforehand that the table would be sufficiently correlated on the
indexed columns for the index to be worthwhile, whereas now there's a
lesser need for the user to know this beforehand.

Also:

<para>
New commands are <command><link linkend="SQL-CREATESTATISTICS">CREATE</></>,
<command><link linkend="SQL-ALTERSTATISTICS">ALTER</></>, and
<command><link linkend="SQL-DROPSTATISTICS">DROP STATISTICS</></>.
This is helpful in
estimating query memory usage and ... HOW IS RATIO USED?
</para>

HOW IS RATIO USED? .... There are two types of new stats;

ndistinct, which can improve row estimations in the query planner for
estimating the number of distinct value groups over multiple columns.
functionaldeps, which provides the planner with a better understanding
of functional depdenences between columns on which the statistics are
defined. The planner takes the functional dependency degree into
account when multiplying selectivity estimations for multiple columns.

Unsure how best to trim that down to something short enough for the
release notes.

--
David Rowley http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services

--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers

On Tue, Apr 25, 2017 at 9:15 AM, Tom Lane <tgl@sss.pgh.pa.us> wrote:

Andres Freund <andres@anarazel.de> writes:

On 2017-04-24 23:37:42 -0400, Bruce Momjian wrote:

I remember seeing those and those are normally details I do not put in
the release notes as there isn't a clear user experience change except
"Postgres is faster". Yeah, a bummer, and I can change my filter, but
it would require discussion.

I think "postgres is faster" is one of the bigger user demands, so I
don't think that policy makes much sense. A large number of the changes
over the next few releases will focus solely on that. Nor do I think
past release notes particularly filtered such changes out.

I think it has been pretty common to accumulate a lot of such changes
into generic entries like, say, "speedups for hash joins". More detail
than that simply isn't useful to end users; and as a rule, our release
notes are too long anyway.

regards, tom lane

Just wondering if the mention of commit
0414b26bac09379a4cbf1fbd847d1cee2293c5e4 is missed? Not sure if this
requires a separate entry or could be merged with -- Support parallel
btree index scans.

--
Regards,
Rafia Sabih
EnterpriseDB: http://www.enterprisedb.com/

--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers

On 2017/04/25 10:31, Bruce Momjian wrote:

I have committed the first draft of the Postgres 10 release notes. They
are current as of two days ago, and I will keep them current. Please
give me any feedback you have.

The only unusual thing is that this release has ~180 items while most
recent release have had ~220. The pattern I see that there are more
large features in this release than previous ones.

Thanks for this.

Wondering if the following really belongs under postgres_fdw improvements:

+<listitem>
+<!--
+Author: Robert Haas <rhaas@postgresql.org>
+2017-03-16 [b30fb56b0] postgres_fdw: Push down <literal>FULL JOIN</>s
with restriction clau
+-->
+<para>
+Improve optimization of <literal>FULL JOIN</> queries containing
subqueries in the
+<literal>FROM</> clause (Etsuro Fujita)
+</para>
+</listitem>

Maybe, nearby the following:

+   <sect3>
+    <title>Additional Modules</title>
...
+<listitem>
+<!--
+Author: Robert Haas <rhaas@postgresql.org>
+2016-10-21 [7012b132d] postgres_fdw: Push down aggregates to remote servers.
+-->
+<para>
+Push aggregates to foreign data wrapper servers, where possible (Jeevan
+Chalke, Ashutosh Bapat)
+</para>

Thanks,
Amit

--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers