Sync addRangeTableEntryForENR() with its peer functions.
addRangeTableEntryForENR had a check for pstate != NULL, which Coverity
pointed out was rather useless since it'd already dereferenced pstate
before that. More to the point, we'd established policy in commit
bc93ac12c that we'd require non-
Fix typo in comment
Author: Masahiko Sawada
Branch
--
master
Details
---
http://git.postgresql.org/pg/commitdiff/c7d225e227aa481c30532b2954055afd1705af31
Modified Files
--
src/backend/access/transam/xlogutils.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
--
Sent
Fix compiler warning
Introduced by 087e696f066d31cb2f1269a1296a13dfe0bf7a11, happens with gcc
4.7.2.
Branch
--
REL9_5_STABLE
Details
---
http://git.postgresql.org/pg/commitdiff/b6e6ae1dc6a647ae6c846c79a8515802a29ebaba
Modified Files
--
src/backend/catalog/objectaddress.c | 4
Fix compiler warning
Introduced by 41306a511c01dd299115cf447858a00e34aebbf6, happens with gcc
4.7.2.
Branch
--
REL9_6_STABLE
Details
---
http://git.postgresql.org/pg/commitdiff/1ec36a9eb4c29dc49838319d1e666f66961d757c
Modified Files
--
src/backend/catalog/objectaddress.c | 4
Ensure BackgroundWorker struct contents are well-defined.
Coverity complained because bgw.bgw_extra wasn't being filled in by
ApplyLauncherRegister(). The most future-proof fix is to memset the
whole BackgroundWorker struct to zeroes. While at it, let's apply the
same coding rule to other places