Re: open items

Hi,

We are down to three open items, all of which have proposed fixes.
That is great, but we need to keep things moving along, because
according to https://wiki.postgresql.org/wiki/PostgreSQL_17_Open_Items
we are due to release beta1 on May 23. That means that a release
freeze will be in effect from Saturday, May 18, which is four days
from now. Since committing patches sometimes leads to unexpected
surprises, it would be best if the proposed fixes were put into place
sooner rather than later, to allow time for any adjustments that may
be required.

* Incorrect Assert in heap_end/rescan for BHS
Melanie posted a new patch version 23 hours ago, Michael Paquier
reviewed it 7 hours ago.
See https://www.postgresql.org/message-id/CAAKRu_a%2B5foybidkmh8FpFAV7iegxetPyPXQ5%3D%2B%2BkqZ%2BZDEUcg%40mail.gmail.com

* Temporal PKs allow duplicates with empty ranges
Peter proposes to revert the feature.
See https://www.postgresql.org/message-id/64c2b2ab-7ce9-475e-ac59-3bfec528bada%40eisentraut.org

* Rename sslnegotiation "requiredirect" option to "directonly"
Latest patch is at
https://www.postgresql.org/message-id/3fdaf4b1-82d1-45bb-8175-f97ff53a1f01%40iki.fi
and, I at least, like it
The basic proposal is to get rid of the idea of having a way to try
both modes (negotiated/direct) and make sslnegotiation just pick one
behavior or the other.

Thanks,

...Robert