tsdb

Bug Description
fix issues found by Coverity Scan in syncMain.c

To Reproduce
N/A

Expected Behavior
fix following issues:
| issue type | category | file path | function | line number |
| -------------------------- | -------------------------- | -------------------------- | -------------------------- |

Is your feature request related to a problem?

We have users periodically asking for week-based partitioning.

Describe the solution you'd like.

Add WEEK to the PARTITION BY options.

Describe alternatives you've considered.

No response

Additional context.

This PR should give enough hints on how to implement this feature: questdb/questdb#1571

示例

• 企业或者组织: 夜莺
• 地点：北京
• 联系方式：contact-us at xxx.com
• 使用场景和经验分享：你们最看重夜莺的哪些功能，解决一个什么样的问题，以及使用规模和范围，使用夜莺监控构建企业级监控体系的过程中，有哪些好的经验分享。
• 需求建议：希望哪些点上夜莺监控能做的更好，更契合您的使用场景。

As an extension to #1960, we should consider adding an alert when ring members are in a non-active state for an unexpected amount of time.

I had suggested something like min by(cluster, namespace) (cortex_ring_members{name="distributor",state!="ACTIVE"}) > 0 for longer than 30min, but feedback from @pracucci highlighted:

• For some components not supporting the auto-forget feature (e.g. dist

Describe this problem

Failed to execute query, err: Server(ServerError { code: 500, msg: "Failed to convert output, query: DROP TABLE demo;. Caused by: Rpc error, code:500, message:Failed to convert output - affected rows: 1" })

A drop table tells one row is affected

Steps to reproduce

drop table demo;

Describe the requested changes:
This page could be simplified. The most impactful change: Do not start with the "Any (No JVM)" version. It forces us to bother users with the Java version, JAVA_HOME env. variable, etc. That's scary, especially for non-Java folks. If we start with the OS-specific versions and leave the "No JVM" version in some "f