Open yazun opened 4 years ago
This error happens also for DML operations. Could anybody comment? Is TBase dependent on the clock synchronisation?
Poking into the code we decided to increase vaccum_delta from default 100 to 10K and it solved the problem for now (we are blocked by #40 ). Logic seems to be scary though as it relies on arbitrary time range. https://github.com/Tencent/TBase/blob/3295393cbabd6f17676c53078cf4cc03aa9dc1fd/src/backend/storage/ipc/procarray.c#L2514 and below.
When a SQL execution time is too long and exceeds vacuum_delta, the timeout SQL will be killed when the vacuum process starts, and the above error will be reported. This problem can be solved by increasing vacuum_delta
pg cluster when you rollback one machine of the cluster, you should rollback the rest ones
pg cluster when you rollback one machine of the cluster, you should rollback the rest ones @ause15 is not rollback automatic on all the nodes?
We experience basic MVCC problem. It never appeared on PG-XL:
Query is read only, but there is some insert/update activity from massive number of clients (500+) executing the same query with different parameters on other tables.
This is a blocker for us as touches fundamentals of the DB. Hoping somebody can support us here. No GTM proxies, GTM is source of transaction IDs.