It is now possible to write in migration `@_plugin_config.foo` where foo is
variable from plugin configuration. Note that configuration typically
belongs to individual services, in catalog this field is called entity. For
migration special values there is special entity called `migration_context`.
So corresponding alter looks this way:

ALTER PLUGIN p 0.1.0 SET migration_context.foo = '"nondefault"'

(extra quotes are temporary, and should be dealt with separately)

Closes https://git.picodata.io/picodata/picodata/picodata/-/issues/659

Previouslly we've blocked on scope termination before reading from
channel, so blocking still occured.

With this patch there is new `blocking` wrapper function that executes
provided closure on separate thread and yields until result is ready

picoplugin -> picodata-plugin
picoplugin_gen -> picodata-plugin-proc-macro

Georgy Moshkin authored 6 months ago and Dmitry Rodionov committed 5 months ago

Previous implementation would call functions over the ffi boundary which
weren't defined with the required `extern` specifiers, which is not allowed.

This commit embeds in plugins a new variable, containing picoplugin
version used to build it. If this version differs from the picodata version
when the plugin gets loaded, the loading fails with an error reporting
the expected and the current versions. This check can be disabled via env
PICODATA_UNSAFE_DISABLE_PLUGIN_COMPATIBILITY_CHECK.

Dmitry Ivanov authored 6 months ago and Dmitry Ivanov committed 6 months ago

Log:

```
i1  | 2024-10-09 02:40:07.850 [135492] main/133/main C> panicked at library/core/src/panicking.rs:221:5:
i1  | panic in a function that cannot unwind
i1  | 2024-10-09 02:40:07.850 [135492] main/133/main C> backtrace:
i1  | disabled backtrace
i1  | 2024-10-09 02:40:07.850 [135492] main/133/main C> aborting due to panic
i1  | [supervisor:135482] no ipc message from child
i1  | [supervisor:135482] subprocess 135492 was signaled with SIGABRT
i1  | [supervisor:135482] core dumped
```

Arseniy Volynets authored 6 months ago and Denis Smirnov committed 6 months ago

Now SQL explain shows the user what buckets the query would be
executed on. Some results are exact, others are not (we return
`buckets: unknown` or `buckets: <= [..]` according to the query).

Add new config::AlterSystemParameters struct which is responsible
for definitions of system parameters, their default values and mapping
to sbroad type.

This is a big step towards moving all system parameters from
_pico_property into another system table.

We pass a timeout into the connection pool call which should be enough

Maksim Kaitmazian authored 6 months ago and Maksim Kaitmazian committed 6 months ago

This commit resolves the performance issues observed in pgbench
benchmark*. Because of the Nagle's algorithm, every message was read with
50ms delay, while the query execution took only 1ms. By disabling the
algorithm via TCP_NODELAY option, we achieve 50 times performance
improvement for a single client in simple query mode.

* https://git.picodata.io/picodata/picodata/picodata/-/issues/1002