1. 23 Dec, 2014 1 commit
    • Matt Stancliff's avatar
      Increase test size for migrating large values · c865809c
      Matt Stancliff authored
      Previously, the old test ran 5,000 loops and used about 500k.
      
      With quicklist, storing those same 5,000 loops takes up 24k, so the
      "large value check" failed!
      
      This increases the test to 20,000 loops which makes the object dump 96k.
      c865809c
  2. 22 May, 2014 1 commit
  3. 09 Jan, 2014 1 commit
  4. 14 Nov, 2012 2 commits
  5. 07 Nov, 2012 2 commits
    • antirez's avatar
      COPY and REPLACE options for MIGRATE. · 1237d71c
      antirez authored
      With COPY now MIGRATE does not remove the key from the source instance.
      With REPLACE it uses RESTORE REPLACE on the target host so that even if
      the key already eixsts in the target instance it will be overwritten.
      
      The options can be used together.
      1237d71c
    • antirez's avatar
      REPLACE option for RESTORE. · e5b5763f
      antirez authored
      The REPLACE option deletes an existing key with the same name (if any)
      and materializes the new one. The default behavior without RESTORE is to
      return an error if a key already exists.
      e5b5763f
  6. 02 Jun, 2012 1 commit
    • Alex Mitrofanov's avatar
      Fixed RESTORE hash failure (Issue #532) · 51857c7e
      Alex Mitrofanov authored
      (additional commit notes by antirez@gmail.com):
      
      The rdbIsObjectType() macro was not updated when the new RDB object type
      of ziplist encoded hashes was added.
      
      As a result RESTORE, that uses rdbLoadObjectType(), failed when a
      ziplist encoded hash was loaded.
      This does not affected normal RDB loading because in that case we use
      the lower-level function rdbLoadType().
      
      The commit also adds a regression test.
      51857c7e
  7. 03 Apr, 2012 1 commit
  8. 02 Apr, 2012 2 commits