First-draft release notes for 11.2.
As usual, the release notes for other branches will be made by cutting
these down, but put them up for community review first.
Branch
--
REL_11_STABLE
Details
---
https://git.postgresql.org/pg/commitdiff/5996cfc4665735a7e6e8d473bd66e8b11e320bbb
Modifi
Defend against null error message reported by libxml2.
While this isn't really supposed to happen, it can occur in OOM
situations and perhaps others. Instead of crashing, substitute
"(no message provided)".
I didn't worry about localizing this text, since we aren't
localizing anything else here;
Defend against null error message reported by libxml2.
While this isn't really supposed to happen, it can occur in OOM
situations and perhaps others. Instead of crashing, substitute
"(no message provided)".
I didn't worry about localizing this text, since we aren't
localizing anything else here;
Defend against null error message reported by libxml2.
While this isn't really supposed to happen, it can occur in OOM
situations and perhaps others. Instead of crashing, substitute
"(no message provided)".
I didn't worry about localizing this text, since we aren't
localizing anything else here;
Defend against null error message reported by libxml2.
While this isn't really supposed to happen, it can occur in OOM
situations and perhaps others. Instead of crashing, substitute
"(no message provided)".
I didn't worry about localizing this text, since we aren't
localizing anything else here;
Defend against null error message reported by libxml2.
While this isn't really supposed to happen, it can occur in OOM
situations and perhaps others. Instead of crashing, substitute
"(no message provided)".
I didn't worry about localizing this text, since we aren't
localizing anything else here;
Defend against null error message reported by libxml2.
While this isn't really supposed to happen, it can occur in OOM
situations and perhaps others. Instead of crashing, substitute
"(no message provided)".
I didn't worry about localizing this text, since we aren't
localizing anything else here;
Doc: fix thinko in description of how to escape a backslash in bytea.
Also clean up some discussion that had been left in a very confused
state thanks to half-hearted adjustments for the change to
standard_conforming_strings being the default.
Discussion:
https://postgr.es/m/154954987367.1297.43
Doc: fix thinko in description of how to escape a backslash in bytea.
Also clean up some discussion that had been left in a very confused
state thanks to half-hearted adjustments for the change to
standard_conforming_strings being the default.
Discussion:
https://postgr.es/m/154954987367.1297.43
Doc: fix thinko in description of how to escape a backslash in bytea.
Also clean up some discussion that had been left in a very confused
state thanks to half-hearted adjustments for the change to
standard_conforming_strings being the default.
Discussion:
https://postgr.es/m/154954987367.1297.43
Doc: fix thinko in description of how to escape a backslash in bytea.
Also clean up some discussion that had been left in a very confused
state thanks to half-hearted adjustments for the change to
standard_conforming_strings being the default.
Discussion:
https://postgr.es/m/154954987367.1297.43
Doc: fix thinko in description of how to escape a backslash in bytea.
Also clean up some discussion that had been left in a very confused
state thanks to half-hearted adjustments for the change to
standard_conforming_strings being the default.
Discussion:
https://postgr.es/m/154954987367.1297.43
Doc: fix thinko in description of how to escape a backslash in bytea.
Also clean up some discussion that had been left in a very confused
state thanks to half-hearted adjustments for the change to
standard_conforming_strings being the default.
Discussion:
https://postgr.es/m/154954987367.1297.43
Alvaro Herrera writes:
> On 2019-Feb-08, Michael Paquier wrote:
>> The timestamp of this commit is a bit messed up:
>> commit: 13b89f96d07ad3da67b57f66c134c3609bd3e98f
>> author: Peter Eisentraut
>> date: Mon, 4 Feb 2019 09:28:17 +0100
>> committer: Peter Eisentraut
>> date: Thu, 7 Feb 2019 08:3
On 08/02/2019 08:45, Michael Paquier wrote:
> The timestamp of this commit is a bit messed up:
Where you say "a bit messed up" one might also say "accurately
reflecting history". :)
--
Peter Eisentraut http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Tra
On 2019-Feb-08, Michael Paquier wrote:
> The timestamp of this commit is a bit messed up:
> commit: 13b89f96d07ad3da67b57f66c134c3609bd3e98f
> author: Peter Eisentraut
> date: Mon, 4 Feb 2019 09:28:17 +0100
> committer: Peter Eisentraut
> date: Thu, 7 Feb 2019 08:34:48 +0100
>
> Perhaps you ove
Fix error handling around ssl_*_protocol_version settings
In case of a reload, we just want to LOG errors instead of FATAL when
processing SSL configuration, but the more recent code for the
ssl_*_protocol_version settings didn't behave like that.
Author: Daniel Gustafsson
Reviewed-by: Michael P
On Fri, Feb 08, 2019 at 10:41:59AM +0100, Peter Eisentraut wrote:
> We usually don't use "namespace" in user-facing error messages. Can you
> change it to say "temporary schema"?
Or just switch to "temporary objects" like it's done on HEAD for the
second message?
Please note that I have kept the
On 18/01/2019 01:22, Michael Paquier wrote:
> Restrict the use of temporary namespace in two-phase transactions
We usually don't use "namespace" in user-facing error messages. Can you
change it to say "temporary schema"?
--
Peter Eisentraut http://www.2ndQuadrant.com/
PostgreSQL De
Add some const decorations
These mainly help understanding the function signatures better.
Branch
--
master
Details
---
https://git.postgresql.org/pg/commitdiff/08d25d7850858094ed6aa7ccc2314f724242336d
Modified Files
--
src/backend/utils/adt/like.c | 14 +++---
20 matches
Mail list logo
