summaryrefslogtreecommitdiff
path: root/async.c
diff options
context:
space:
mode:
authormichael-grunder <michael.grunder@gmail.com>2020-12-15 17:46:11 -0800
committermichael-grunder <michael.grunder@gmail.com>2021-04-02 09:34:09 -0700
commit6204182aae71ca321418c069eac907936eeaa33a (patch)
tree498503f7e814222e7b506e9756a9e1903e119943 /async.c
parentd6a0b192b414dc261589d4c2d16577c2192b39c0 (diff)
Handle the case where an invalidation is sent second.
RESP3 invalidation messages always seemed to be sent before the response to a given command, but it appears this is not always the case: In Redis 6.2.0RC1 Redis sends the invalidation after the HSET in the following sequence: ``` hget hash field $5 value hset hash field value :0 >2 $10 invalidate *1 $4 hash ``` To account for this possibility just wrap redisGetReplyFromReader in a loop as it is called twice in redisGetReply.
Diffstat (limited to 'async.c')
0 files changed, 0 insertions, 0 deletions