aboutsummaryrefslogtreecommitdiff
path: root/src/test
diff options
context:
space:
mode:
authorAmit Kapila <akapila@postgresql.org>2019-12-12 11:51:30 +0530
committerAmit Kapila <akapila@postgresql.org>2019-12-17 09:46:49 +0530
commitfc68a10b573faababd3a7d2b3f1f703a8ae76a44 (patch)
tree715cde8b8b8d26bf640e1a1b804079e152a00158 /src/test
parent2cf51809b1ae072d2f086286456e1e29e234a2a8 (diff)
downloadpostgresql-fc68a10b573faababd3a7d2b3f1f703a8ae76a44.tar.gz
postgresql-fc68a10b573faababd3a7d2b3f1f703a8ae76a44.zip
Change overly strict Assert in TransactionGroupUpdateXidStatus.
This Assert thought that an overflowed transaction can never get registered for the group update.  But that is not true, because even when the number of children for a transaction got reduced, the overflow flag is not changed. And, for group update, we only care about the current number of children for a transaction that is being committed. Based on comments by Andres Freund, remove a redundant Assert in TransactionIdSetPageStatus as we already had a static Assert for the same condition a few lines earlier. Reported-by: Vignesh C Author: Dilip Kumar Reviewed-by: Amit Kapila Backpatch-through: 11 Discussion: https://postgr.es/m/CAFiTN-s5=uJw-Z6JC9gcqtBSjXsrHnU63PXBrA=pnBjqnkm5UA@mail.gmail.com
Diffstat (limited to 'src/test')
0 files changed, 0 insertions, 0 deletions