This could occur with extremely large planner estimates
for the size of a hashjoin's result.

Fix very rare crash in inet/cidr comparisons
(Chris Mikkelson)

Ensure that shared tuple-level locks held by prepared
transactions are not ignored (Heikki)

Fix premature drop of temporary files used for a cursor
that is accessed within a subtransaction (Heikki)

Fix memory leak in syslogger process when rotating to a
new CSV logfile (Tom)

Fix Windows permission-downgrade logic (Jesse
Morris)

This fixes some cases where the database failed to start
on Windows, often with misleading error messages such as
"could not locate matching postgres
executable".

Fix incorrect logic for GiST index page splits, when the
split depends on a non-first column of the index (Paul
Ramsey)

Don't error out if recycling or removing an old WAL file
fails at the end of checkpoint (Heikki)

It's better to treat the problem as non-fatal and allow
the checkpoint to complete. Future checkpoints will retry
the removal. Such problems are not expected in normal
operation, but have been seen to be caused by misdesigned
Windows anti-virus and backup software.

Ensure WAL files aren't repeatedly archived on Windows
(Heikki)

This is another symptom that could happen if some other
process interfered with deletion of a no-longer-needed
file.

Fix PAM password processing to be more robust (Tom)

The previous code is known to fail with the combination
of the Linux pam_krb5 PAM module
with Microsoft Active Directory as the domain controller.
It might have problems elsewhere too, since it was making
unjustified assumptions about what arguments the PAM stack
would pass to it.