Closes #1130

Yaroslav Dynnikov authored 1 year ago and Georgy Moshkin committed 1 year ago

Follow-up for 2b1bd622

> submodule.<name>.branch
>
> A remote branch name for tracking updates in the upstream submodule.
> If the option is not specified, it defaults to the remote HEAD.

The `origin/HEAD` is the default branch in GitLab. In case of
tarantool-sys nowadays it corresponds to `2.11.0-picodata`.

This option is responsible for the correct operation of

    git submodule update --remote tarantool-sys

Maksim Kaitmazian authored 1 year ago and Denis Smirnov committed 1 year ago

Protocol has been moved to a separate repository called pgproto,
so there is no need to store it here anymore.

This allows to operate submodule with the one-liner:

```
git submodule update --remote tarantool-sys/
```

This patch also updates the submodule in a mentioned way.

This patch brings stored procedures that manage postgres server.

Current commit introduces distributed SQL in picodata (we use
'sbroad' library). Now it is possible to execute cluster-wide
SQL with 'pico.sql([[query]], {params})' lua method.

Current limitations:
1. DDL is still not implemented in picodata, so space sharding
   is mocked by '_pico_space' space (we'll remove it later).
2. We still have duplicating symbols of the Tarantool module in
   sbroad and in picodata rlibs.
3. We need to reuse piocdata's sharding functions and handle the
   case when different spaces in the query have different sharding
   functions.

Co-authored-by: Georgy Moshkin <gmoshkin@picodata.io>

Thanks to the updates in tarantool module we don't use tarantool
symbols to work with decimal. As a bonus we can remove our mocking
framework with dynamic linking of the decNumber library to cargo
test binary.

Now coordinator dispatches SQL patterns with separated parameters.
It would help us to cache patterns on the segments as prepared
statements one day and skip SQL parsing.

Also we have faced a Tarantool bug

https://github.com/tarantool/tarantool/issues/7283

and made a hot fix in the Picodata fork. As a result we have also
migrated sbroad CI to our fork.

We migrate from the `decimal` crate (used decQuad from decNumber
to store the numbers) to Tarantool internal types provided by the
Rust module. The reason was to make IR numeric values easy
serializable to the query parameters (a part of the executor
refactoring).

The problem with Tarantool internal types is that the internal
decNumber representation is provided by Tarantool ABI. So we always
need Tarantool itself to use the types. It is ok for integration
tests, but for unit tests with `cargo test` it is a problem. As a
solution we have implemented some mocking infrastructure to build
a static library based on the Tarantool decNumber, MsgPuck and some
wrappers over them both to make unit tests work.

+ tarantool-sys submodule
+ tarantool-patches directory
+ build.rs build script to patch and build tarantool
+ static linking with tarantool
+ refactoring for cli arguments