gooderp18绿色标准版
Nie możesz wybrać więcej, niż 25 tematów Tematy muszą się zaczynać od litery lub cyfry, mogą zawierać myślniki ('-') i mogą mieć do 35 znaków.

435 lines
26KB

  1. <?xml version="1.0" encoding="UTF-8" standalone="no"?>
  2. <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"><html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>E.2. Release 12.3</title><link rel="stylesheet" type="text/css" href="stylesheet.css" /><link rev="made" href="pgsql-docs@lists.postgresql.org" /><meta name="generator" content="DocBook XSL Stylesheets V1.79.1" /><link rel="prev" href="release-12-4.html" title="E.1. Release 12.4" /><link rel="next" href="release-12-2.html" title="E.3. Release 12.2" /></head><body><div xmlns="http://www.w3.org/TR/xhtml1/transitional" class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="5" align="center">E.2. Release 12.3</th></tr><tr><td width="10%" align="left"><a accesskey="p" href="release-12-4.html" title="E.1. Release 12.4">Prev</a> </td><td width="10%" align="left"><a accesskey="u" href="release.html" title="Appendix E. Release Notes">Up</a></td><th width="60%" align="center">Appendix E. Release Notes</th><td width="10%" align="right"><a accesskey="h" href="index.html" title="PostgreSQL 12.4 Documentation">Home</a></td><td width="10%" align="right"> <a accesskey="n" href="release-12-2.html" title="E.3. Release 12.2">Next</a></td></tr></table><hr></hr></div><div class="sect1" id="RELEASE-12-3"><div class="titlepage"><div><div><h2 class="title" style="clear: both">E.2. Release 12.3</h2></div></div></div><div class="toc"><dl class="toc"><dt><span class="sect2"><a href="release-12-3.html#id-1.11.6.6.4">E.2.1. Migration to Version 12.3</a></span></dt><dt><span class="sect2"><a href="release-12-3.html#id-1.11.6.6.5">E.2.2. Changes</a></span></dt></dl></div><p><strong>Release date: </strong>2020-05-14</p><p>
  3. This release contains a variety of fixes from 12.2.
  4. For information about new features in major release 12, see
  5. <a class="xref" href="release-12.html" title="E.5. Release 12">Section E.5</a>.
  6. </p><div class="sect2" id="id-1.11.6.6.4"><div class="titlepage"><div><div><h3 class="title">E.2.1. Migration to Version 12.3</h3></div></div></div><p>
  7. A dump/restore is not required for those running 12.X.
  8. </p><p>
  9. However, if you are upgrading from a version earlier than 12.2,
  10. see <a class="xref" href="release-12-2.html" title="E.3. Release 12.2">Section E.3</a>.
  11. </p></div><div class="sect2" id="id-1.11.6.6.5"><div class="titlepage"><div><div><h3 class="title">E.2.2. Changes</h3></div></div></div><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem"><p>
  12. Fix possible failure with <code class="literal">GENERATED</code> columns
  13. (David Rowley)
  14. </p><p>
  15. If a <code class="literal">GENERATED</code> column's value is an exact copy of
  16. another column of the table (and it is a pass-by-reference data
  17. type), it was possible to crash or insert corrupted data into the
  18. table. While it would be rather pointless for
  19. a <code class="literal">GENERATED</code> expression to just duplicate another
  20. column, an expression using a function that sometimes returns its
  21. input unchanged could create the situation.
  22. </p></li><li class="listitem"><p>
  23. Handle inheritance of generated columns better (Peter Eisentraut)
  24. </p><p>
  25. When a table column is inherited during <code class="command">CREATE TABLE
  26. ... INHERITS</code>, disallow changing any generation properties
  27. when the parent column is already
  28. marked <code class="literal">GENERATED</code>; but allow a child column to be
  29. marked <code class="literal">GENERATED</code> when its parent is not.
  30. </p></li><li class="listitem"><p>
  31. Fix cross-column references in <code class="command">CREATE TABLE LIKE INCLUDING
  32. GENERATED</code> (Peter Eisentraut)
  33. </p><p>
  34. <code class="command">CREATE TABLE ... LIKE</code> failed when trying to copy
  35. a <code class="literal">GENERATED</code> expression that references a
  36. physically-later column.
  37. </p></li><li class="listitem"><p>
  38. Propagate <code class="command">ALTER TABLE ... SET STORAGE</code> to indexes
  39. (Peter Eisentraut)
  40. </p><p>
  41. Non-expression index columns have always copied
  42. the <code class="structfield">attstorage</code> property of their table
  43. column at creation. Update them when <code class="command">ALTER TABLE ... SET
  44. STORAGE</code> is done, to maintain consistency.
  45. </p></li><li class="listitem"><p>
  46. Preserve the <code class="structfield">indisclustered</code> setting of
  47. indexes rewritten by <code class="command">ALTER TABLE</code> (Amit Langote,
  48. Justin Pryzby)
  49. </p><p>
  50. Previously, <code class="command">ALTER TABLE</code> lost track of which index
  51. had been used for <code class="command">CLUSTER</code>.
  52. </p></li><li class="listitem"><p>
  53. Preserve the replica identity properties of indexes rewritten
  54. by <code class="command">ALTER TABLE</code> (Quan Zongliang, Peter Eisentraut)
  55. </p></li><li class="listitem"><p>
  56. Preserve the <code class="structfield">indisclustered</code> setting of
  57. indexes rebuilt by <code class="command">REINDEX CONCURRENTLY</code>
  58. (Justin Pryzby)
  59. </p></li><li class="listitem"><p>
  60. Lock objects sooner during <code class="command">DROP OWNED BY</code>
  61. (Álvaro Herrera)
  62. </p><p>
  63. This avoids failures in race-condition cases where another session is
  64. deleting some of the same objects.
  65. </p></li><li class="listitem"><p>
  66. Fix error-case processing for <code class="command">CREATE ROLE ... IN
  67. ROLE</code> (Andrew Gierth)
  68. </p><p>
  69. Some error cases would be reported as <span class="quote">“<span class="quote">unexpected node
  70. type</span>”</span> or the like, instead of the intended message.
  71. </p></li><li class="listitem"><p>
  72. Ensure that when a partition is detached, any triggers cloned from
  73. its formerly-parent table are removed (Justin Pryzby)
  74. </p></li><li class="listitem"><p>
  75. Fix crash when <code class="literal">COLLATE</code> is applied to a
  76. non-collatable type in a partition bound expression (Dmitry Dolgov)
  77. </p></li><li class="listitem"><p>
  78. Ensure that unique indexes over partitioned tables match the
  79. equality semantics of the partitioning key (Guancheng Luo)
  80. </p><p>
  81. This would only be an issue with index opclasses that have unusual
  82. notions of equality, but it's wrong in theory, so check.
  83. </p></li><li class="listitem"><p>
  84. Ensure that members of the <code class="literal">pg_read_all_stats</code> role
  85. can read all statistics views, as expected (Magnus Hagander)
  86. </p><p>
  87. The functions underlying
  88. the <code class="structname">pg_stat_progress_*</code> views had not gotten
  89. this memo.
  90. </p></li><li class="listitem"><p>
  91. Repair performance regression in
  92. <code class="structname">information_schema</code>.<code class="structname">triggers</code>
  93. view (Tom Lane)
  94. </p><p>
  95. This patch redefines that view so that an
  96. outer <code class="literal">WHERE</code> clause constraining the table name
  97. can be pushed down into the view, allowing its calculations to be
  98. done only for triggers belonging to the table of interest rather
  99. than all triggers in the database. In a database with many triggers
  100. this would make a significant speed difference for queries of that
  101. form. Since things worked that way before v11, this is a potential
  102. performance regression. Users who find this to be a problem can fix
  103. it by replacing the view definition (or, perhaps, just deleting and
  104. reinstalling the whole <code class="structname">information_schema</code>
  105. schema).
  106. </p></li><li class="listitem"><p>
  107. Repair performance regression in floating point overflow/underflow
  108. detection (Emre Hasegeli)
  109. </p><p>
  110. Previous refactoring had resulted in <code class="function">isinf()</code>
  111. being called extra times in some hot code paths.
  112. </p></li><li class="listitem"><p>
  113. Fix full text search to handle NOT above a phrase search correctly
  114. (Tom Lane)
  115. </p><p>
  116. Queries such as <code class="literal">!(foo&lt;-&gt;bar)</code> failed to find
  117. matching rows when implemented as a GiST or GIN index search.
  118. </p></li><li class="listitem"><p>
  119. Fix full text search for cases where a phrase search includes an
  120. item with both prefix matching and a weight restriction (Tom Lane)
  121. </p></li><li class="listitem"><p>
  122. Fix <code class="function">ts_headline()</code> to make better headline
  123. selections when working with phrase queries (Tom Lane)
  124. </p></li><li class="listitem"><p>
  125. Fix bugs in <code class="varname">gin_fuzzy_search_limit</code> processing
  126. (Adé Heyward, Tom Lane)
  127. </p><p>
  128. A small value of <code class="varname">gin_fuzzy_search_limit</code> could
  129. result in unexpected slowness due to unintentionally rescanning the
  130. same index page many times. Another code path failed to apply the
  131. intended filtering at all, possibly returning too many values.
  132. </p></li><li class="listitem"><p>
  133. Allow input of type <code class="type">circle</code> to accept the format
  134. <span class="quote">“<span class="quote"><code class="literal">(<em class="replaceable"><code>x</code></em>,<em class="replaceable"><code>y</code></em>),<em class="replaceable"><code>r</code></em></code></span>”</span>
  135. as the documentation says it does (David Zhang)
  136. </p></li><li class="listitem"><p>
  137. Make the <code class="function">get_bit()</code>
  138. and <code class="function">set_bit()</code> functions cope
  139. with <code class="type">bytea</code> strings longer than 256MB (Movead Li)
  140. </p><p>
  141. Since the bit number argument is only <code class="type">int4</code>, it's
  142. impossible to use these functions to access bits beyond the first
  143. 256MB of a long <code class="type">bytea</code>. We'll widen the argument
  144. to <code class="type">int8</code> in v13, but in the meantime, allow these
  145. functions to work on the initial substring of a
  146. long <code class="type">bytea</code>.
  147. </p></li><li class="listitem"><p>
  148. Ignore file-not-found errors in <code class="function">pg_ls_waldir()</code>
  149. and allied functions (Tom Lane)
  150. </p><p>
  151. This prevents a race condition failure if a file is removed between
  152. when we see its directory entry and when we attempt
  153. to <code class="function">stat()</code> it.
  154. </p></li><li class="listitem"><p>
  155. Avoid possibly leaking an open-file descriptor for a directory
  156. in <code class="function">pg_ls_dir()</code>,
  157. <code class="function">pg_timezone_names()</code>,
  158. <code class="function">pg_tablespace_databases()</code>, and allied functions
  159. (Justin Pryzby)
  160. </p></li><li class="listitem"><p>
  161. Fix polymorphic-function type resolution to correctly infer the
  162. actual type of an <code class="type">anyarray</code> output when given only
  163. an <code class="type">anyrange</code> input (Tom Lane)
  164. </p></li><li class="listitem"><p>
  165. Fix server's connection-startup logic for case where a GSSAPI
  166. connection is rejected because support is not compiled in, and the
  167. client then tries SSL instead (Andrew Gierth)
  168. </p><p>
  169. This led to a bogus <span class="quote">“<span class="quote">unsupported frontend protocol</span>”</span>
  170. failure.
  171. </p></li><li class="listitem"><p>
  172. Fix memory leakage during GSSAPI encryption (Tom Lane)
  173. </p><p>
  174. Both the backend and libpq would leak memory equivalent to the total
  175. amount of data sent during the session, if GSSAPI encryption is in use.
  176. </p></li><li class="listitem"><p>
  177. Fix query-lifespan memory leak for a set-returning function used in
  178. a query's <code class="literal">FROM</code> clause (Andres Freund)
  179. </p></li><li class="listitem"><p>
  180. Avoid leakage of a hashed subplan's hash tables across multiple
  181. executions (Andreas Karlsson, Tom Lane)
  182. </p><p>
  183. This mistake could result in severe memory bloat if a query
  184. re-executed a hashed subplan enough times.
  185. </p></li><li class="listitem"><p>
  186. Improve planner's handling of no-op domain coercions (Tom Lane)
  187. </p><p>
  188. Fix some cases where a domain coercion that does nothing was not
  189. completely removed from expressions.
  190. </p></li><li class="listitem"><p>
  191. Avoid unlikely crash when <code class="command">REINDEX</code> is terminated
  192. by a session-shutdown signal (Tom Lane)
  193. </p></li><li class="listitem"><p>
  194. Prevent printout of possibly-incorrect hash join table statistics
  195. in <code class="command">EXPLAIN</code> (Konstantin Knizhnik, Tom Lane, Thomas
  196. Munro)
  197. </p></li><li class="listitem"><p>
  198. Fix reporting of elapsed time for heap truncation steps
  199. in <code class="command">VACUUM VERBOSE</code> (Tatsuhito Kasahara)
  200. </p></li><li class="listitem"><p>
  201. Fix possible undercounting of deleted B-tree index pages
  202. in <code class="command">VACUUM VERBOSE</code> output (Peter Geoghegan)
  203. </p></li><li class="listitem"><p>
  204. Fix wrong bookkeeping for oldest deleted page in a B-tree index
  205. (Peter Geoghegan)
  206. </p><p>
  207. This could cause subtly wrong decisions about
  208. when <code class="command">VACUUM</code> can skip an index cleanup scan;
  209. although it appears there may be no significant user-visible effects
  210. from that.
  211. </p></li><li class="listitem"><p>
  212. Ensure that TimelineHistoryRead and TimelineHistoryWrite wait states
  213. are reported in all code paths that read or write timeline history
  214. files (Masahiro Ikeda)
  215. </p></li><li class="listitem"><p>
  216. Avoid possibly showing <span class="quote">“<span class="quote">waiting</span>”</span> twice in a process's
  217. PS status (Masahiko Sawada)
  218. </p></li><li class="listitem"><p>
  219. Avoid race condition when <code class="command">ANALYZE</code> replaces the
  220. catalog tuple for extended statistics data (Dean Rasheed)
  221. </p></li><li class="listitem"><p>
  222. Remove ill-considered skip of <span class="quote">“<span class="quote">redundant</span>”</span>
  223. anti-wraparound vacuums (Michael Paquier)
  224. </p><p>
  225. This avoids a corner case where autovacuum could get into a loop of
  226. repeatedly trying and then skipping the same vacuum job.
  227. </p></li><li class="listitem"><p>
  228. Ensure INCLUDE'd columns are always removed from B-tree pivot tuples
  229. (Peter Geoghegan)
  230. </p><p>
  231. This mistake wasted space in some rare cases, but was otherwise
  232. harmless.
  233. </p></li><li class="listitem"><p>
  234. Cope with invalid TOAST indexes that could be left over after a
  235. failed <code class="command">REINDEX CONCURRENTLY</code> (Julien Rouhaud)
  236. </p></li><li class="listitem"><p>
  237. Ensure that valid index dependencies are left behind after a
  238. failed <code class="command">REINDEX CONCURRENTLY</code> (Michael Paquier)
  239. </p><p>
  240. Previously the old index could be left with
  241. no <code class="structname">pg_depend</code> links at all, so that for
  242. example it would not get dropped if the parent table is dropped.
  243. </p></li><li class="listitem"><p>
  244. Avoid failure if autovacuum tries to access a just-dropped temporary
  245. schema (Tom Lane)
  246. </p><p>
  247. This hazard only arises if a superuser manually drops a temporary
  248. schema; which isn't normal practice, but should work.
  249. </p></li><li class="listitem"><p>
  250. Avoid premature recycling of WAL segments during crash recovery
  251. (Jehan-Guillaume de Rorthais)
  252. </p><p>
  253. WAL segments that become ready to be archived during crash recovery
  254. were potentially recycled without being archived.
  255. </p></li><li class="listitem"><p>
  256. Avoid scanning irrelevant timelines during archive recovery (Kyotaro
  257. Horiguchi)
  258. </p><p>
  259. This can eliminate many attempts to fetch non-existent WAL files from
  260. archive storage, which is helpful if archive access is slow.
  261. </p></li><li class="listitem"><p>
  262. Remove bogus <span class="quote">“<span class="quote">subtransaction logged without previous top-level
  263. txn record</span>”</span> error check in logical decoding (Arseny Sher,
  264. Amit Kapila)
  265. </p><p>
  266. This condition is legitimately reachable in various scenarios, so
  267. remove the check.
  268. </p></li><li class="listitem"><p>
  269. Avoid possible failure after a replication slot copy, due to
  270. premature removal of WAL data (Masahiko Sawada, Arseny Sher)
  271. </p></li><li class="listitem"><p>
  272. Ensure that a replication
  273. slot's <code class="literal">io_in_progress_lock</code> is released in failure
  274. code paths (Pavan Deolasee)
  275. </p><p>
  276. This could result in a walsender later becoming stuck waiting for
  277. the lock.
  278. </p></li><li class="listitem"><p>
  279. Ensure that generated columns are correctly handled during updates
  280. issued by logical replication (Peter Eisentraut)
  281. </p></li><li class="listitem"><p>
  282. Fix race conditions in synchronous standby management (Tom Lane)
  283. </p><p>
  284. During a change in the <code class="varname">synchronous_standby_names</code>
  285. setting, there was a window in which wrong decisions could be made
  286. about whether it is OK to release transactions that are waiting for
  287. synchronous commit. Another hazard for similarly wrong decisions
  288. existed if a walsender process exited and was immediately replaced
  289. by another.
  290. </p></li><li class="listitem"><p>
  291. Add missing SQLSTATE values to a few error reports (Sawada Masahiko)
  292. </p></li><li class="listitem"><p>
  293. Fix PL/pgSQL to reliably refuse to execute an event trigger function
  294. as a plain function (Tom Lane)
  295. </p></li><li class="listitem"><p>
  296. Fix memory leak in <span class="application">libpq</span> when
  297. using <code class="literal">sslmode=verify-full</code> (Roman Peshkurov)
  298. </p><p>
  299. Certificate verification during connection startup could leak some
  300. memory. This would become an issue if a client process opened many
  301. database connections during its lifetime.
  302. </p></li><li class="listitem"><p>
  303. Fix <span class="application">ecpg</span> to treat an argument of
  304. just <span class="quote">“<span class="quote"><code class="literal">-</code></span>”</span> as meaning <span class="quote">“<span class="quote">read
  305. from stdin</span>”</span> on all platforms (Tom Lane)
  306. </p></li><li class="listitem"><p>
  307. Fix crash in <span class="application">psql</span> when attempting to
  308. re-establish a failed connection (Michael Paquier)
  309. </p></li><li class="listitem"><p>
  310. Allow tab-completion of the filename argument
  311. to <span class="application">psql</span>'s <code class="command">\gx</code> command
  312. (Vik Fearing)
  313. </p></li><li class="listitem"><p>
  314. Add <span class="application">pg_dump</span> support for <code class="command">ALTER
  315. ... DEPENDS ON EXTENSION</code> (Álvaro Herrera)
  316. </p><p>
  317. <span class="application">pg_dump</span> previously ignored dependencies added
  318. this way, causing them to be forgotten during dump/restore or
  319. <span class="application">pg_upgrade</span>.
  320. </p></li><li class="listitem"><p>
  321. Fix <span class="application">pg_dump</span> to dump comments on RLS
  322. policy objects (Tom Lane)
  323. </p></li><li class="listitem"><p>
  324. In <span class="application">pg_dump</span>, postpone restore of event
  325. triggers till the end (Fabrízio de Royes Mello, Hamid Akhtar,
  326. Tom Lane)
  327. </p><p>
  328. This minimizes the risk that an event trigger could interfere with
  329. the restoration of other objects.
  330. </p></li><li class="listitem"><p>
  331. Ensure that <span class="application">pg_basebackup</span> generates valid
  332. tar files (Robert Haas)
  333. </p><p>
  334. In some cases a partial block of zeroes would be added to the end of
  335. the file. While this seems to be harmless with common versions of
  336. tar, it's not OK per the POSIX file format spec.
  337. </p></li><li class="listitem"><p>
  338. Make <span class="application">pg_checksums</span> skip tablespace
  339. subdirectories that belong to a
  340. different <span class="productname">PostgreSQL</span> major version
  341. (Michael Banck, Bernd Helmle)
  342. </p><p>
  343. Such subdirectories don't really belong to our database cluster, and
  344. so must not be processed.
  345. </p></li><li class="listitem"><p>
  346. Ignore temporary copies of <code class="filename">pg_internal.init</code>
  347. in <span class="application">pg_checksums</span> and related
  348. programs (Michael Paquier)
  349. </p></li><li class="listitem"><p>
  350. Fix quoting of <code class="option">--encoding</code>, <code class="option">--lc-ctype</code>
  351. and <code class="option">--lc-collate</code> values
  352. in <span class="application">createdb</span> utility (Michael Paquier)
  353. </p></li><li class="listitem"><p>
  354. <code class="filename">contrib/lo</code>'s <code class="function">lo_manage()</code>
  355. function crashed if called directly rather than as a trigger (Tom
  356. Lane)
  357. </p></li><li class="listitem"><p>
  358. In <code class="filename">contrib/ltree</code>,
  359. protect against overflow of <code class="type">ltree</code>
  360. and <code class="type">lquery</code> length fields (Nikita Glukhov)
  361. </p></li><li class="listitem"><p>
  362. Work around failure in <code class="filename">contrib/pageinspect</code>'s
  363. <code class="function">bt_metap()</code> function when an oldest_xact value
  364. exceeds 2^31-1 (Peter Geoghegan)
  365. </p><p>
  366. Such XIDs will now be reported as negative integers, which isn't
  367. great but it beats throwing an error. v13 will widen the output
  368. argument to <code class="type">int8</code> to provide saner reporting.
  369. </p></li><li class="listitem"><p>
  370. Fix cache reference leak in <code class="filename">contrib/sepgsql</code>
  371. (Michael Luo)
  372. </p></li><li class="listitem"><p>
  373. On Windows, avoid premature creation of postmaster's log file
  374. during <code class="literal">pg_ctl start</code> (Alexander Lakhin)
  375. </p><p>
  376. The previous coding could allow the file to be created with
  377. permissions that wouldn't allow the postmaster to write on it.
  378. </p></li><li class="listitem"><p>
  379. Avoid failures when dealing with Unix-style locale names on
  380. Windows (Juan José Santamaría Flecha)
  381. </p></li><li class="listitem"><p>
  382. On Windows, set console VT100 compatibility mode in
  383. programs that support <code class="varname">PG_COLOR</code> colorization
  384. (Juan José Santamaría Flecha)
  385. </p><p>
  386. Without this, the colorization option doesn't actually work.
  387. </p></li><li class="listitem"><p>
  388. Stop requiring extra parentheses in <code class="function">ereport()</code>
  389. calls (Andres Freund, Tom Lane)
  390. </p></li><li class="listitem"><p>
  391. Use <span class="application">pkg-config</span>, if available, to
  392. locate <span class="application">libxml2</span>
  393. during <span class="application">configure</span> (Hugh McMaster, Tom
  394. Lane, Peter Eisentraut)
  395. </p><p>
  396. If <span class="application">pkg-config</span> is not present or lacks
  397. knowledge of <span class="application">libxml2</span>, we still
  398. query <span class="application">xml2-config</span> as before.
  399. </p><p>
  400. This change could break build processes that try to
  401. make <span class="productname">PostgreSQL</span> use a non-default version
  402. of <span class="application">libxml2</span> by putting that
  403. version's <span class="application">xml2-config</span> into
  404. the <code class="varname">PATH</code>. Instead,
  405. set <code class="varname">XML2_CONFIG</code> to point to the
  406. non-default <span class="application">xml2-config</span>. That method
  407. will work with either older or
  408. newer <span class="productname">PostgreSQL</span> releases.
  409. </p></li><li class="listitem"><p>
  410. Fix Makefile dependencies for <span class="application">libpq</span>
  411. and <span class="application">ecpg</span> (Dagfinn Ilmari Mannsåker)
  412. </p></li><li class="listitem"><p>
  413. In MSVC builds, cope with spaces in the path name for Python
  414. (Victor Wagner)
  415. </p></li><li class="listitem"><p>
  416. In MSVC builds, fix detection of Visual Studio version to work with
  417. more language settings (Andrew Dunstan)
  418. </p></li><li class="listitem"><p>
  419. In MSVC builds, use <code class="literal">-Wno-deprecated</code> with bison
  420. versions newer than 3.0, as non-Windows builds already do (Andrew
  421. Dunstan)
  422. </p></li><li class="listitem"><p>
  423. Update time zone data files to <span class="application">tzdata</span>
  424. release 2020a for DST law changes in Morocco and the Canadian Yukon,
  425. plus historical corrections for Shanghai.
  426. </p><p>
  427. The America/Godthab zone has been renamed to America/Nuuk to reflect
  428. current English usage; however, the old name remains available as a
  429. compatibility link.
  430. </p><p>
  431. Also, update <span class="application">initdb</span>'s list of known
  432. Windows time zone names to include recent additions, improving the
  433. odds that it will correctly translate the system time zone setting
  434. on that platform.
  435. </p></li></ul></div></div></div><div class="navfooter"><hr /><table width="100%" summary="Navigation footer"><tr><td width="40%" align="left"><a accesskey="p" href="release-12-4.html">Prev</a> </td><td width="20%" align="center"><a accesskey="u" href="release.html">Up</a></td><td width="40%" align="right"> <a accesskey="n" href="release-12-2.html">Next</a></td></tr><tr><td width="40%" align="left" valign="top">E.1. Release 12.4 </td><td width="20%" align="center"><a accesskey="h" href="index.html">Home</a></td><td width="40%" align="right" valign="top"> E.3. Release 12.2</td></tr></table></div></body></html>
上海开阖软件有限公司 沪ICP备12045867号-1