00980_merge_alter_settings is flaky #82933
Description
Interesting thing that between 50f1402 (CI) and 779e921 (CI) the error changed
From
2025-06-13 10:06:29 Expected server error code '115' but got no server error (query: ALTER TABLE table_for_alter MODIFY SETTING xxx_yyy=124; -- { serverError UNKNOWN_SETTING }).
2025-06-13 10:06:29 Error on processing query: Code: 32. DB::Exception: Attempt to read after eof: while receiving packet from localhost:9000. (ATTEMPT_TO_READ_AFTER_EOF) (version 25.6.1.2888 (official build))
2025-06-13 10:06:29 (query: ALTER TABLE table_for_alter MODIFY SETTING xxx_yyy=124; -- { serverError UNKNOWN_SETTING })
2025-06-15 09:01:57 Error on processing query: Code: 32. DB::Exception: Attempt to read after eof: while receiving packet from localhost:9000. (ATTEMPT_TO_READ_AFTER_EOF) (version 25.6.1.3007 (official build))
2025-06-15 09:01:57 (query: DETACH TABLE table_for_alter;)
But the underlying problem is the same, apparently in case of failed INSERT it interpret the next line as a setting
2025.06.15 09:01:57.896252 [ 894958 ] {50567557-ce7d-4f8a-bc66-2117fe1aeb0c} <Error> executeQuery: Code: 252. DB::Exception: Too many parts (1 with average size of 320.00 B) in table 'test_9quobynp.table_for_alter (9c3af391-2bbe-4fe3-a5b2-26b2e7be7a4c)'. Merges are processing significantly slower than inserts. (TOO_MANY_PARTS) (version 25.6.1.3007 (official build)) (from [::1]:48438) (comment: 00980_merge_alter_settings.sql) (query 12, line 31) (in query: INSERT INTO table_for_alter VALUES ), Stack trace (when copying this message, always include the lines below):
...
2025.06.15 09:01:57.897120 [ 894958 ] {50567557-ce7d-4f8a-bc66-2117fe1aeb0c} <Warning> Settings: Unknown setting 'DETACH TABLE table_for_alter;', skipping
2025.06.15 09:01:57.897222 [ 894958 ] {50567557-ce7d-4f8a-bc66-2117fe1aeb0c} <Error> TCPHandler: Can't send logs or exception to client. Close connection.: Code: 101. DB::Exception: Unexpected packet Query received from client. (UNEXPECTED_PACKET_FROM_CLIENT), Stack trace (when copying this message, always include the lines below):