diff options
| author | Tom Lane <tgl@sss.pgh.pa.us> | 2019-10-04 10:34:21 -0400 |
|---|---|---|
| committer | Tom Lane <tgl@sss.pgh.pa.us> | 2019-10-04 10:34:40 -0400 |
| commit | 61aa9f544a91f2908e4c7cd549907cdc5b6f1c82 (patch) | |
| tree | a0b3d61330501010ba6864849415b1d241237730 /src/backend/commands/trigger.c | |
| parent | f2369bc610a19563cc00054ccfe9089fac469641 (diff) | |
| download | postgresql-61aa9f544a91f2908e4c7cd549907cdc5b6f1c82.tar.gz postgresql-61aa9f544a91f2908e4c7cd549907cdc5b6f1c82.zip | |
Fix bitshiftright()'s zero-padding some more.
Commit 5ac0d9360 failed to entirely fix bitshiftright's habit of
leaving one-bits in the pad space that should be all zeroes,
because in a moment of sheer brain fade I'd concluded that only
the code path used for not-a-multiple-of-8 shift distances needed
to be fixed. Of course, a multiple-of-8 shift distance can also
cause the problem, so we need to forcibly zero the extra bits
in both cases.
Per bug #16037 from Alexander Lakhin. As before, back-patch to all
supported branches.
Discussion: https://postgr.es/m/16037-1d1ebca564db54f4@postgresql.org
Diffstat (limited to 'src/backend/commands/trigger.c')
0 files changed, 0 insertions, 0 deletions