@@ -232,8 +232,15 @@ Branch: master [9b42e7137] 2019-05-13 10:27:59 -0700
232232Branch: REL_11_STABLE [bf78f50ba] 2019-05-13 10:27:57 -0700
233233-->
234234 <para>
235- Avoid corruption of a btree index in the unlikely case that a failure
236- occurs during key truncation during a page split (Peter Geoghegan)
235+ Avoid writing an invalid empty btree index page in the unlikely case
236+ that a failure occurs while processing INCLUDEd columns during a page
237+ split (Peter Geoghegan)
238+ </para>
239+
240+ <para>
241+ The invalid page would not affect normal index operations, but it
242+ might cause failures in subsequent VACUUMs. If that has happened to
243+ one of your indexes, recover by reindexing the index.
237244 </para>
238245 </listitem>
239246
@@ -340,17 +347,39 @@ Branch: REL_10_STABLE [8de574aa8] 2019-06-14 11:25:13 -0400
340347Branch: REL9_6_STABLE [75b0f21e1] 2019-06-14 11:25:13 -0400
341348Branch: REL9_5_STABLE [77dc741a1] 2019-06-14 11:25:13 -0400
342349Branch: REL9_4_STABLE [37011bcb3] 2019-06-14 11:25:13 -0400
350+ Author: Andrew Gierth <rhodiumtoad@postgresql.org>
351+ Branch: master [e3846a00c] 2019-06-15 18:15:23 +0100
352+ Branch: REL_11_STABLE [7f28fc8e9] 2019-06-15 18:16:43 +0100
353+ Branch: REL_10_STABLE [2913a892e] 2019-06-15 18:18:03 +0100
354+ Branch: REL9_6_STABLE [5f5b6667e] 2019-06-15 18:19:30 +0100
355+ Branch: REL9_5_STABLE [6335f8a99] 2019-06-15 18:21:41 +0100
356+ Branch: REL9_4_STABLE [6c66865f3] 2019-06-15 18:23:16 +0100
343357-->
344358 <para>
345- Make <application>initdb</application> determine the operating
346- system's time zone from the <filename>/etc/localtime</filename>
347- symbolic link, if that exists (Tom Lane)
359+ Improve <application>initdb</application>'s handling of multiple
360+ equivalent names for the system time zone (Tom Lane, Andrew Gierth)
361+ </para>
362+
363+ <para>
364+ Make <application>initdb</application> examine
365+ the <filename>/etc/localtime</filename> symbolic link, if that
366+ exists, to break ties between equivalent names for the system time
367+ zone. This makes <application>initdb</application> more likely to
368+ select the time zone name that the user would expect when multiple
369+ identical time zones exist. It will not change the behavior
370+ if <filename>/etc/localtime</filename> is not a symlink to a zone
371+ data file, nor if the time zone is determined from
372+ the <envar>TZ</envar> environment variable.
348373 </para>
349374
350375 <para>
351- This makes <application>initdb</application> more likely to select
352- the desired time zone string when multiple identical time zones
353- exist.
376+ Separately, prefer <literal>UTC</literal> over other spellings of
377+ that time zone, when neither <envar>TZ</envar>
378+ nor <filename>/etc/localtime</filename> provide a hint. This fixes
379+ an annoyance introduced by <application>tzdata</application> 2019a's
380+ change to make the <literal>UCT</literal> and <literal>UTC</literal>
381+ zone names equivalent: <application>initdb</application> was then
382+ preferring <literal>UCT</literal>, which almost nobody wants.
354383 </para>
355384 </listitem>
356385