This should fix Issue 332: when there is a background process saving we still allow the hash tables to grow, but only when a critical treshold is reached. Formerly we prevented the resize at all triggering pathological O(N) behavior. Also there is a fix for the statistics in INFO about the number of keys expired

Thanks to sylr@github
Signed-off-by: NPedro Melo <melo@simplicidade.org>

Signed-off-by: NPedro Melo <melo@simplicidade.org>

Signed-off-by: NPedro Melo <melo@simplicidade.org>

redis-cli does no longer try to auto detect if it is used inside a pipe. To read last argument from stdandard input there is to use the -x option. This will make it playing better inside cron scripts and in general when stdin is hacked.

Fix re-enabled again, I forgot to check if VM was enabled before calling handleClientsBlockedOnSwappedKey()

Fixed a race condition in VM happening when a key was deleted while there was a client waiting for this key to be resumed from swap to memory. The client would hang forever.

When creating the readable event results in an error (this happens when
the server hits OS limits), the client was not added to the list of
clients when freeClient was called. This results in an assertion error.
It is better to check this condition first and free the client
immediately when this condition occurs. Port of 00a90feb.

Resolved conflict in src/db.c and changed adding an error to the reply
in blockingPopGenericCommand to use the new API.