just fieldobj itself as sentinel of the fact a field object is used or not, instead of using the filed length, that may be confusing both for people and for the compiler emitting a warning.
lookupKeyByPattern() was implemented with a trick to speedup the lookup process allocating two fake Redis obejcts on the stack. However now that we propagate expires to the slave as DEL operations the lookup of the key may result into a call to expireIfNeeded() having the stack allocated object as argument, that may in turn use it to create the protocol to send to the slave. But since this fake obejcts are inherently read-only this is a problem. As a side effect of this fix there are no longer size limits in the pattern to be used with GET/BY option of SORT. See antirez#460 for bug details.
…onds initialized correctly to avoid strange INFO output at startup when a slave has yet to connect to its master.
…hem) when SLAVEOF turns a master into a slave.
…o a more acceptable value of 50.
…gigabyte). Memtest86 and Memtester links are also displayed while running the test.
…e branch (pipelining,run selected tests,fixes)
centos) as well as debian/ubuntu
…t. The original patch was reworked a bit.
…o the server.
…end inside the data set when loading very old RDB files produced by early-stage versions of Redis.