</para>
<para>
- Also, if you are upgrading from a version earlier than 8.4.10,
- see the release notes for 8.4.10.
+ However, if you are upgrading from a version earlier than 8.4.17,
+ see the release notes for 8.4.17.
</para>
</sect2>
<listitem>
<para>
- Prevent downcasing of non-ASCII non-double-quoted identifiers in
- multi-byte encodings (Andrew Dunstan)
+ Prevent corruption of multi-byte characters when attempting to
+ case-fold identifiers (Andrew Dunstan)
</para>
<para>
- The previous behavior was wrong and confusing.
+ <productname>PostgreSQL</> case-folds non-ASCII characters only
+ when using a single-byte server encoding.
</para>
</listitem>
<listitem>
<para>
- Fix libpq SSL deadlock bug (Stephen Frost)
+ Fix deadlock bug in libpq when using SSL (Stephen Frost)
</para>
</listitem>
</para>
<para>
- Previously such push downs could generate errors.
+ Subqueries of a <literal>UNION</> or <literal>INTERSECT</> that
+ contain set-returning functions or volatile functions in their
+ <literal>SELECT</> lists could be improperly optimized, leading to
+ run-time errors or incorrect query results.
</para>
</listitem>
<listitem>
<para>
- Fix rare <literal>GROUP BY</> query error caused by improperly
- processed data type modifiers (Tom Lane)
+ Fix rare case of <quote>failed to locate grouping columns</>
+ planner failure (Tom Lane)
</para>
</listitem>
<listitem>
<para>
- Allow view dump code to better handle dropped columns on base tables
- (Tom Lane)
+ Improve view dumping code's handling of dropped columns in referenced
+ tables (Tom Lane)
</para>
</listitem>
<listitem>
<para>
- Allow various spellings of infinity on all platforms (Tom Lane)
+ Ensure that floating-point data input accepts standard spellings
+ of <quote>infinity</> on all platforms (Tom Lane)
</para>
<para>
- Supported infinity values are "inf", "+inf", "-inf", "infinity",
- "+infinity", and "-infinity".
+ The C99 standard says that allowable spellings are <literal>inf</>,
+ <literal>+inf</>, <literal>-inf</>, <literal>infinity</>,
+ <literal>+infinity</>, and <literal>-infinity</>. Make sure we
+ recognize these even if the platform's <function>strtod</> function
+ doesn't.
</para>
</listitem>
<listitem>
<para>
Update time zone data files to <application>tzdata</> release 2013d
- for DST law changes in DST law changes in Israel, Morocco, Palestine,
- Paraguay. Also, historical zone data corrections for Macquarie Island
- (Tom Lane)
+ for DST law changes in Israel, Morocco, Palestine, and Paraguay.
+ Also, historical zone data corrections for Macquarie Island.
</para>
</listitem>
</para>
<para>
- Also, if you are upgrading from a version earlier than 9.0.6,
- see the release notes for 9.0.6.
+ However, if you are upgrading from a version earlier than 9.0.13,
+ see the release notes for 9.0.13.
</para>
</sect2>
<listitem>
<para>
- Prevent downcasing of non-ASCII non-double-quoted identifiers in
- multi-byte encodings (Andrew Dunstan)
+ Prevent corruption of multi-byte characters when attempting to
+ case-fold identifiers (Andrew Dunstan)
</para>
<para>
- The previous behavior was wrong and confusing.
+ <productname>PostgreSQL</> case-folds non-ASCII characters only
+ when using a single-byte server encoding.
</para>
</listitem>
<listitem>
<para>
- Fix libpq SSL deadlock bug (Stephen Frost)
+ Fix deadlock bug in libpq when using SSL (Stephen Frost)
</para>
</listitem>
<listitem>
<para>
- Fix possible SSL network stack corruption in threaded libpq applications
+ Fix possible SSL state corruption in threaded libpq applications
(Nick Phillips, Stephen Frost)
</para>
</listitem>
</para>
<para>
- Previously such push downs could generate errors.
+ Subqueries of a <literal>UNION</> or <literal>INTERSECT</> that
+ contain set-returning functions or volatile functions in their
+ <literal>SELECT</> lists could be improperly optimized, leading to
+ run-time errors or incorrect query results.
</para>
</listitem>
<listitem>
<para>
- Fix rare <literal>GROUP BY</> query error caused by improperly
- processed data type modifiers (Tom Lane)
+ Fix rare case of <quote>failed to locate grouping columns</>
+ planner failure (Tom Lane)
</para>
</listitem>
<listitem>
<para>
- Allow view dump code to better handle dropped columns on base tables
- (Tom Lane)
+ Improve view dumping code's handling of dropped columns in referenced
+ tables (Tom Lane)
</para>
</listitem>
<para>
Specifically, lessen keyword restrictions for role names, language
names, <command>EXPLAIN</> and <command>COPY</> options, and
- <command>SET</> values. This allows <literal>COPY ... (FORMAT
- BINARY)</> previously <literal>BINARY</> required single-quotes.
+ <command>SET</> values. This allows <literal>COPY ... (FORMAT
+ BINARY)</> to work as expected; previously <literal>BINARY</> needed
+ to be quoted.
</para>
</listitem>
<listitem>
<para>
- Improve analyze statistics generation after a cancelled file truncate
- request (Kevin Grittner)
+ Ensure that <command>VACUUM ANALYZE</> still runs the ANALYZE phase
+ if its attempt to truncate the file is cancelled due to lock conflicts
+ (Kevin Grittner)
</para>
</listitem>
<listitem>
<para>
- Allow various spellings of infinity on all platforms (Tom Lane)
+ Ensure that floating-point data input accepts standard spellings
+ of <quote>infinity</> on all platforms (Tom Lane)
</para>
<para>
- Supported infinity values are "inf", "+inf", "-inf", "infinity",
- "+infinity", and "-infinity".
+ The C99 standard says that allowable spellings are <literal>inf</>,
+ <literal>+inf</>, <literal>-inf</>, <literal>infinity</>,
+ <literal>+infinity</>, and <literal>-infinity</>. Make sure we
+ recognize these even if the platform's <function>strtod</> function
+ doesn't.
</para>
</listitem>
<listitem>
<para>
Update time zone data files to <application>tzdata</> release 2013d
- for DST law changes in DST law changes in Israel, Morocco, Palestine,
- Paraguay. Also, historical zone data corrections for Macquarie Island
- (Tom Lane)
+ for DST law changes in Israel, Morocco, Palestine, and Paraguay.
+ Also, historical zone data corrections for Macquarie Island.
</para>
</listitem>
</para>
<para>
- Also, if you are upgrading from a version earlier than 9.1.6,
- see the release notes for 9.1.6.
+ However, if you are upgrading from a version earlier than 9.1.9,
+ see the release notes for 9.1.9.
</para>
</sect2>
<listitem>
<para>
- Prevent downcasing of non-ASCII non-double-quoted identifiers in
- multi-byte encodings (Andrew Dunstan)
+ Prevent corruption of multi-byte characters when attempting to
+ case-fold identifiers (Andrew Dunstan)
</para>
<para>
- The previous behavior was wrong and confusing.
+ <productname>PostgreSQL</> case-folds non-ASCII characters only
+ when using a single-byte server encoding.
</para>
</listitem>
<listitem>
<para>
- Fix libpq SSL deadlock bug (Stephen Frost)
+ Fix deadlock bug in libpq when using SSL (Stephen Frost)
</para>
</listitem>
<listitem>
<para>
- Fix possible SSL network stack corruption in threaded libpq applications
+ Fix possible SSL state corruption in threaded libpq applications
(Nick Phillips, Stephen Frost)
</para>
</listitem>
</para>
<para>
- Previously such push downs could generate errors.
+ Subqueries of a <literal>UNION</> or <literal>INTERSECT</> that
+ contain set-returning functions or volatile functions in their
+ <literal>SELECT</> lists could be improperly optimized, leading to
+ run-time errors or incorrect query results.
</para>
</listitem>
<listitem>
<para>
- Fix rare <literal>GROUP BY</> query error caused by improperly
- processed data type modifiers (Tom Lane)
+ Fix rare case of <quote>failed to locate grouping columns</>
+ planner failure (Tom Lane)
</para>
</listitem>
<listitem>
<para>
- Allow view dump code to better handle dropped columns on base tables
- (Tom Lane)
+ Improve view dumping code's handling of dropped columns in referenced
+ tables (Tom Lane)
</para>
</listitem>
<para>
Specifically, lessen keyword restrictions for role names, language
names, <command>EXPLAIN</> and <command>COPY</> options, and
- <command>SET</> values. This allows <literal>COPY ... (FORMAT
- BINARY)</> previously <literal>BINARY</> required single-quotes.
+ <command>SET</> values. This allows <literal>COPY ... (FORMAT
+ BINARY)</> to work as expected; previously <literal>BINARY</> needed
+ to be quoted.
</para>
</listitem>
<listitem>
<para>
- Have <application>pg_upgrade</> use <command>pg_dump
+ Make <application>pg_upgrade</> use <literal>pg_dump
--quote-all-identifiers</> to avoid problems with keyword changes
between releases (Tom Lane)
</para>
<listitem>
<para>
- Improve analyze statistics generation after a cancelled file truncate
- request (Kevin Grittner)
+ Ensure that <command>VACUUM ANALYZE</> still runs the ANALYZE phase
+ if its attempt to truncate the file is cancelled due to lock conflicts
+ (Kevin Grittner)
</para>
</listitem>
<listitem>
<para>
- Allow various spellings of infinity on all platforms (Tom Lane)
+ Ensure that floating-point data input accepts standard spellings
+ of <quote>infinity</> on all platforms (Tom Lane)
</para>
<para>
- Supported infinity values are "inf", "+inf", "-inf", "infinity",
- "+infinity", and "-infinity".
+ The C99 standard says that allowable spellings are <literal>inf</>,
+ <literal>+inf</>, <literal>-inf</>, <literal>infinity</>,
+ <literal>+infinity</>, and <literal>-infinity</>. Make sure we
+ recognize these even if the platform's <function>strtod</> function
+ doesn't.
</para>
</listitem>
<listitem>
<para>
Update time zone data files to <application>tzdata</> release 2013d
- for DST law changes in DST law changes in Israel, Morocco, Palestine,
- Paraguay. Also, historical zone data corrections for Macquarie Island
- (Tom Lane)
+ for DST law changes in Israel, Morocco, Palestine, and Paraguay.
+ Also, historical zone data corrections for Macquarie Island.
</para>
</listitem>
</para>
<para>
- Also, if you are upgrading from a version earlier than 9.2.2,
- see the release notes for 9.2.2.
+ However, if you are upgrading from a version earlier than 9.2.4,
+ see the release notes for 9.2.4.
</para>
</sect2>
<listitem>
<para>
- Prevent downcasing of non-ASCII non-double-quoted identifiers in
- multi-byte encodings (Andrew Dunstan)
+ Prevent corruption of multi-byte characters when attempting to
+ case-fold identifiers (Andrew Dunstan)
</para>
<para>
- The previous behavior was wrong and confusing.
+ <productname>PostgreSQL</> case-folds non-ASCII characters only
+ when using a single-byte server encoding.
</para>
</listitem>
<listitem>
<para>
- Fix memory leak when creating range indexes (Heikki Linnakangas)
+ Fix memory leak when creating B-tree indexes on range columns
+ (Heikki Linnakangas)
</para>
</listitem>
<listitem>
<para>
- Fix libpq SSL deadlock bug (Stephen Frost)
+ Fix deadlock bug in libpq when using SSL (Stephen Frost)
</para>
</listitem>
<listitem>
<para>
- Fix possible SSL network stack corruption in threaded libpq applications
+ Fix possible SSL state corruption in threaded libpq applications
(Nick Phillips, Stephen Frost)
</para>
</listitem>
<listitem>
<para>
- Fix <literal>UNION ALL</> and inheritance queries to properly
- recheck parameterized paths (Tom Lane)
+ Fix accounting for qualifier evaluation costs in <literal>UNION ALL</>
+ and inheritance queries (Tom Lane)
</para>
<para>
- This fixes cases where suboptimal query plans could potentially be
- chosen.
+ This fixes cases where suboptimal query plans could be chosen if
+ some <literal>WHERE</> clauses are expensive to calculate.
</para>
</listitem>
</para>
<para>
- Previously such push downs could generate errors.
+ Subqueries of a <literal>UNION</> or <literal>INTERSECT</> that
+ contain set-returning functions or volatile functions in their
+ <literal>SELECT</> lists could be improperly optimized, leading to
+ run-time errors or incorrect query results.
</para>
</listitem>
<listitem>
<para>
- Fix rare <literal>GROUP BY</> query error caused by improperly
- processed data type modifiers (Tom Lane)
+ Fix rare case of <quote>failed to locate grouping columns</>
+ planner failure (Tom Lane)
</para>
</listitem>
<listitem>
<para>
- Allow view dump code to better handle dropped columns on base tables
- (Tom Lane)
+ Improve view dumping code's handling of dropped columns in referenced
+ tables (Tom Lane)
</para>
</listitem>
<para>
Specifically, lessen keyword restrictions for role names, language
names, <command>EXPLAIN</> and <command>COPY</> options, and
- <command>SET</> values. This allows <literal>COPY ... (FORMAT
- BINARY)</> previously <literal>BINARY</> required single-quotes.
+ <command>SET</> values. This allows <literal>COPY ... (FORMAT
+ BINARY)</> to work as expected; previously <literal>BINARY</> needed
+ to be quoted.
</para>
</listitem>
<listitem>
<para>
- Have <application>pg_upgrade</> use <command>>pg_dump
+ Make <application>pg_upgrade</> use <literal>pg_dump
--quote-all-identifiers</> to avoid problems with keyword changes
between releases (Tom Lane)
</para>
<listitem>
<para>
- Improve analyze statistics generation after a cancelled file truncate
- request (Kevin Grittner)
+ Ensure that <command>VACUUM ANALYZE</> still runs the ANALYZE phase
+ if its attempt to truncate the file is cancelled due to lock conflicts
+ (Kevin Grittner)
</para>
</listitem>
<listitem>
<para>
- Allow various spellings of infinity on all platforms (Tom Lane)
+ Ensure that floating-point data input accepts standard spellings
+ of <quote>infinity</> on all platforms (Tom Lane)
</para>
<para>
- Supported infinity values are "inf", "+inf", "-inf", "infinity",
- "+infinity", and "-infinity".
+ The C99 standard says that allowable spellings are <literal>inf</>,
+ <literal>+inf</>, <literal>-inf</>, <literal>infinity</>,
+ <literal>+infinity</>, and <literal>-infinity</>. Make sure we
+ recognize these even if the platform's <function>strtod</> function
+ doesn't.
</para>
</listitem>
<listitem>
<para>
Update time zone data files to <application>tzdata</> release 2013d
- for DST law changes in DST law changes in Israel, Morocco, Palestine,
- Paraguay. Also, historical zone data corrections for Macquarie Island
- (Tom Lane)
+ for DST law changes in Israel, Morocco, Palestine, and Paraguay.
+ Also, historical zone data corrections for Macquarie Island.
</para>
</listitem>
A dump/restore is not required for those running 9.3.X.
</para>
+ <para>
+ However, if you use the <literal>hstore</> extension, see the
+ first changelog entry.
+ </para>
+
</sect2>
<sect2>
<listitem>
<para>
- Update hstore extension with JSON functionality (Andrew Dunstan)
+ Ensure new-in-9.3 JSON functionality is added to the <literal>hstore</>
+ extension during an update (Andrew Dunstan)
</para>
<para>
- Users who installed hstore prior to 9.3.1 must execute:
+ Users who upgraded a pre-9.3 database containing <literal>hstore</>
+ should execute
<programlisting>
ALTER EXTENSION hstore UPDATE;
</programlisting>
- to add two new JSON functions and a cast.
+ after installing 9.3.1, to add two new JSON functions and a cast.
+ (If <literal>hstore</> is already up to date, this command does
+ nothing.)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Fix memory leak when creating B-tree indexes on range columns
+ (Heikki Linnakangas)
</para>
</listitem>
<listitem>
<para>
- Fix memory leak when creating range indexes (Heikki Linnakangas)
+ Fix memory leak caused by <function>lo_open()</function> failure
+ (Heikki Linnakangas)
</para>
</listitem>
<listitem>
<para>
- Fix libpq SSL deadlock bug (Stephen Frost)
+ Fix deadlock bug in libpq when using SSL (Stephen Frost)
</para>
</listitem>