Matt Stancliff d8c7db1bdb Improve RDB error-on-load handling
Previouly if we loaded a corrupt RDB, Redis printed an error report
with a big "REPORT ON GITHUB" message at the bottom.  But, we know
RDB load failures are corrupt data, not corrupt code.

Now when RDB failure is detected (duplicate keys or unknown data
types in the file), we run check-rdb against the RDB then exit.  The
automatic check-rdb hopefully gives the user instant feedback
about what is wrong instead of providing a mysterious stack
trace.
2015-01-28 11:19:00 -05:00
..
2012-04-13 17:52:33 -07:00
2014-09-29 06:49:07 -04:00
2014-08-08 10:43:54 +02:00
2013-01-19 10:59:44 +01:00
2014-12-12 12:02:39 +09:00
2015-01-23 18:10:14 +01:00
2014-12-14 12:25:42 +02:00
2014-07-02 17:04:14 +02:00
2014-08-08 14:54:02 +02:00
2014-12-23 09:31:02 -05:00
2015-01-02 11:16:08 -05:00
2014-08-08 10:05:32 +02:00
2015-01-28 11:19:00 -05:00
2015-01-08 09:52:55 +01:00
2014-12-23 09:31:03 -05:00
2015-01-02 11:16:08 -05:00
2014-07-02 16:31:22 +02:00
2014-12-21 16:13:45 +02:00
2011-07-06 15:22:00 +02:00
2015-01-02 11:16:08 -05:00
2015-01-02 11:16:08 -05:00