Dmitry Ivanov authored 5 months ago and Dmitry Ivanov committed 5 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 5 months ago and Denis Smirnov committed 5 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 5 months ago and Maksim Kaitmazian committed 5 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

Denis Smirnov authored 5 months ago and Dmitry Rodionov committed 5 months ago

There was a bug when SQL statistics LRU removed some old query
from the _sql_query table. The query ref_counter field in unsigned,
but the code decremented it below zero in the space on eviction.
That produced an error (fixed).

Should read footer as:

References #991
Closes #943

Дмитрий Кольцов authored 5 months ago and Dmitry Rodionov committed 5 months ago

Due to the bug in RPC (see https://git.picodata.io/picodata/picodata/picodata/-/issues/991)
RPC call timeout does not account TCP connection establishment.
So a request to a peer without a connection was not aborted
due to timeout.
Force a timeout directly for a future returned by RPC to avoid this

Closes #991