Currently executing queries like: 

```
SELECT * FROM system.tables LIMIT 10;\G 
SELECT * FROM system.tables LIMIT 10\G;
```

Ends up with a syntax error.

From the documentation, it should not be an error:

> You can specify \G instead of or after the semicolon.


return MultiQueryProcessingStage::QUERIES_END;
    if (this_query_begin >= all_queries_end)
        return MultiQueryProcessingStage::QUERIES_END;
    // Remove leading empty newlines and other whitespace, because they
    // are annoying to filter in query log. This is mostly relevant for
    // the tests.
    while (this_query_ueries_end && isWhitespaceASCII(*this_query_begin))
        ++this_query_begin;
    if (this_query_begin >= all_queries_end)
        return MultiQueryProcessingStage::QUERIES_END;
    // If there are only comments left until the end of file, we just
    // stop. The parser can't handle this situation because it always
    // expects that there is some query that it can parse.
    // We can get into this situation because the parser also doesn't
    // skip the trailing comments after parsing a query. This is because
    // they may as well be the leading comments for the next query,
    // and it makes more sense to treat them as such.
    {
        Tokens tokens(this_query_begin, all_queries_end
        IParser::Pos token_iterator(tokens, global_context->getSettingsRef().max_parser_depth
        if (!token_iterator.isValid())
            return MultiQueryProcessingStage::QUERIES_END;
    }
    this_query_end = this_query_begin;
    try
    {
        parsed_query = parseQuery(th all_queries_end, true
    }
    catch (Exception & e)
    {