Existance of node/rel is checked before deletion
Fixed issue with prematurely exhausted iterator.

By exhausting the iterator on initialization, some queries lead to a lot
of unnecessary dbhits, e.g.
````
profile MATCH (n:topic)-[r]->(m:topic) return n,r,m limit 1;

+------------------+------+----------+-------------+----------------------+
|         Operator | Rows |   DbHits | Identifiers |                Other |
+------------------+------+----------+-------------+----------------------+
|            Slice |    1 |        0 |             |         {  AUTOINT0} |
|           Filter |    1 |        1 |             | hasLabel(m:topic(0)) |
| TraversalMatcher |    1 | 11292978 |             |              m, r, m |
+------------------+------+----------+-------------+----------------------+

Total database accesses: 11292979
````
should ideally only touch a small portion of the graph but ends up touching something like
50% instead. This fix I believe fix this.
Merge pull request #3697 from lutovich/2.1-double-delete-of-rel-rollbacks-tx

Existance of node/rel is checked before deletion
Merge 2.1-maint in master

Conflicts:
	community/kernel/src/main/java/org/neo4j/kernel/impl/api/LockingStatementOperations.java
	community/kernel/src/main/java/org/neo4j/kernel/impl/api/StateHandlingStatementOperations.java
	community/kernel/src/main/java/org/neo4j/kernel/impl/api/store/CacheLayer.java
	community/kernel/src/main/java/org/neo4j/kernel/impl/api/store/PersistenceCache.java
Fix the manual build
Revert "Removed outdated scripts and man pages" and "Fix the manual build"

This reverts commit c431cd803b911213e5d9382a7fa8f2883d8a7272 and f0ffe0dc26cf09629ae71eb8ba113606ad338f53.
Merge pull request #3499 from pontusmelke/bug-exhaust-iterator

Fixed issue with prematurely exhausted iterator.
Merge remote-tracking branch 'upstream/1.9-maint' into 2.0-maint

Conflicts:
	community/kernel/src/main/java/org/neo4j/kernel/impl/traversal/TraverserImpl.java
	community/kernel/src/main/java/org/neo4j/kernel/impl/traversal/TraverserIterator.java
Merge branch '2.0-maint' into 2.1-maint
Merge branch '2.1-maint'
Log rotation won't happen on kernel panic

Log rotation checks that the kernel is still healthy, while having the
logFile lock, before doing the rotation. This to be on the safe side in
the event of panic, ehere the next recovery will have a chance to repair
the damages if all transactions are still in the active log.

For this the TransactionAppender#append method decides on success or panic
while holding the logFile lock and therefore safely communicates this
state to any log rotation happening concurrently.