Hi,
Well, it depends what a "difficult state" is.
Both Ctrl+C and "kill -9" should work with the default settings, meaning it
should not leave the database in an inconsistent state. If it doesn't, that
would be a bug. There are quite many tests for this actually. If you have a
simple, reproducibl
Is there a reliable way to stop the db when it's stuck on a data load
that's taking too long? Very frequently it becomes unresponsive to ^C, or
other signals. kill -9 is the only thing I've found that works, which
leaves the db in a difficult state.
This happens with LOG=1, so not just a LOG=0
