On 2017-11-03 12:36:59 -0700, Peter Geoghegan wrote:
> Andres Freund wrote:
> > Here's that patch. I've stared at this some, and Robert did too. Robert
> > mentioned that the commit message might need some polish and I'm not
> > 100% sure about the error message texts yet.
>
> The commit message
ecpg: Use bool instead of int
Use "bool" for Boolean variables, rather than "int", matching backend
change f505edace12655f3491b9c91991731e2b6bf1f0b.
Reviewed-by: Michael Paquier
Branch
--
master
Details
---
https://git.postgresql.org/pg/commitdiff/4703a480a9e15f8b8b481dac44f2e36a4a687f
Fix incorrect use of bool
NSUnLinkModule() doesn't take a bool as second argument but one of set
of specific constants. The numeric values are the same in this case,
but clean it up while we're cleaning up bool use elsewhere.
Reviewed-by: Michael Paquier
Branch
--
master
Details
---
h
ecpg: Remove useless return values
Remove useless or inconsistently used return values from functions,
matching backend changes 99bf328237d89e0fd22821a940d4af0506353218 and
791359fe0eae83641f0929159d5861359d395e97.
Reviewed-by: Michael Paquier
Branch
--
master
Details
---
https://git.p
On 2017-11-04 06:15:00 -0700, Andres Freund wrote:
> The current testcase, and I think the descriptions in the relevant
> threads, all actually fail to point out the precise way the bug is
> triggered. As e.g. evidenced that the freeze-the-dead case appears to
> not cause any failures in !assertio
doc: Update text for new recovery_target_lsn setting
Reported-by: Tomonari Katsumata
Author: Michael Paquier
Branch
--
master
Details
---
https://git.postgresql.org/pg/commitdiff/bc105c4be057177c6fe7bd93b31eb1dc66ed4395
Modified Files
--
doc/src/sgml/recovery-config.sgml |
doc: Update text for new recovery_target_lsn setting
Reported-by: Tomonari Katsumata
Author: Michael Paquier
Branch
--
REL_10_STABLE
Details
---
https://git.postgresql.org/pg/commitdiff/c3f43a71663cdb9d589f536b544b03675f13e14f
Modified Files
--
doc/src/sgml/recovery-config
First-draft release notes for 10.1.
As usual, the release notes for other branches will be made by cutting
these down, but put them up for community review first. Note that a
fair percentage of the entries apply only to prior branches because
their issue was already fixed in 10.0.
Branch
--