|
35 | 35 |
|
36 | 36 | <listitem> |
37 | 37 | <!-- |
| 38 | +Author: Peter Eisentraut <peter_e@gmx.net> |
| 39 | +Branch: master [7c7d4fdda] 2016-04-08 14:11:56 -0400 |
| 40 | +Branch: REL9_5_STABLE [a3c17b2af] 2016-05-06 23:47:42 -0400 |
| 41 | +Branch: REL9_4_STABLE [e3b14de9f] 2016-05-07 00:10:31 -0400 |
| 42 | +Branch: REL9_3_STABLE [a9d8644de] 2016-05-07 00:10:17 -0400 |
| 43 | +Branch: REL9_2_STABLE [e3a493ac0] 2016-05-07 00:05:39 -0400 |
| 44 | +Branch: REL9_1_STABLE [9b676fd49] 2016-05-07 00:09:37 -0400 |
| 45 | +--> |
| 46 | + <para> |
| 47 | + Clear the OpenSSL error queue before OpenSSL calls, rather than |
| 48 | + assuming it's clear already; and make sure we leave it clear |
| 49 | + (Peter Geoghegan, Dave Vitek, Peter Eisentraut) |
| 50 | + </para> |
| 51 | + |
| 52 | + <para> |
| 53 | + This avoids problems when there are multiple connections using |
| 54 | + OpenSSL within a single process and not all the code involved |
| 55 | + follows the same rules for when to clear the error queue. |
| 56 | + While the problem is worse for <application>libpq</>, it's |
| 57 | + possible for it to arise within the server as well. |
| 58 | + </para> |
| 59 | + </listitem> |
| 60 | + |
| 61 | + <listitem> |
| 62 | +<!-- |
38 | 63 | Author: Tom Lane <tgl@sss.pgh.pa.us> |
39 | 64 | Branch: master [80f66a9ad] 2016-04-21 20:05:58 -0400 |
40 | 65 | Branch: REL9_5_STABLE [94c685a7c] 2016-04-21 20:05:58 -0400 |
@@ -286,6 +311,29 @@ Branch: REL9_1_STABLE [3ef1f3a3e] 2016-04-13 18:57:52 -0400 |
286 | 311 |
|
287 | 312 | <listitem> |
288 | 313 | <!-- |
| 314 | +Author: Tom Lane <tgl@sss.pgh.pa.us> |
| 315 | +Branch: master [1a2c17f8e] 2016-05-06 22:05:56 -0400 |
| 316 | +Branch: REL9_5_STABLE [196870f2f] 2016-05-06 22:05:51 -0400 |
| 317 | +Branch: REL9_4_STABLE [e1aecebc0] 2016-05-06 22:05:51 -0400 |
| 318 | +Branch: REL9_3_STABLE [e1d88f983] 2016-05-06 22:05:51 -0400 |
| 319 | +--> |
| 320 | + <para> |
| 321 | + Fix <application>pg_upgrade</> to not fail when new-cluster TOAST rules |
| 322 | + differ from old (Tom Lane) |
| 323 | + </para> |
| 324 | + |
| 325 | + <para> |
| 326 | + <application>pg_upgrade</> had special-case code to handle the |
| 327 | + situation where the new <productname>PostgreSQL</> version thinks that |
| 328 | + a table should have a TOAST table while the old version did not. That |
| 329 | + code was broken, so remove it; there seems no reason to believe that we |
| 330 | + can't get along fine without a TOAST table if that was okay according |
| 331 | + to the old version's rules. |
| 332 | + </para> |
| 333 | + </listitem> |
| 334 | + |
| 335 | + <listitem> |
| 336 | +<!-- |
289 | 337 | Author: Noah Misch <noah@leadboat.com> |
290 | 338 | Branch: master [213c7df03] 2016-04-26 21:53:58 -0400 |
291 | 339 | Branch: REL9_5_STABLE [f9989482d] 2016-04-26 21:54:07 -0400 |
|