Sergey Chernov

Is this change requires rebase now? Please let us know - we also need this feature. Thanks!

@haishui126 thank you for the contribution! I see some steps have failed. We fixed the issue. Would you please pull latest changes to the branch to verify the fix in...

@haishui126 Thank you! I see @mshustov triggered the CI (thank you) and it is passed.

Good day, there is a similar issue for java client https://github.com/ClickHouse/clickhouse-java/issues/1529 I believe root cause is in multithreaded access. I have a tests that reproduces the problem. However fix would...

Good day, @Evre-wuwy! What clickhouse-java client version do you use? Have you tried with latest? Would you please add more information: - exception stack trace - logs showing the problem...

Good day, @jiqimaogou ! Would you please explain the purpose of `cityHash64`? Thanks!

@mohaidoss There is a bug on client side - value from the server timezone header is not applied to results (only for RowBinary*) I'm working on the fix.

Client today doesn't read `X-Server-Timezone` from a response. The `toDateTime('2023-10-04 10:54:36')` will be in server or session timezone and thus no conversion should be: ``` SELECT toDateTime('2023-10-04 10:54:36'), serverTimezone(), timezone(),...

I was able to reproduce the problem with multiple threads. Fixing this would need some refactoring.

If statements are called from different threads then it is clear what happening: ``` pool-1-thread-1: Executing select 1 queryID Optional[b48cef26-a612-4196-b779-df87e6a5a174] queryId: b48cef26-a612-4196-b779-df87e6a5a174 pool-1-thread-2: Executing select 1 queryID Optional[91bfa2ec-3767-4207-8f69-f4b5836512b5] queryId: 91bfa2ec-3767-4207-8f69-f4b5836512b5...