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

可以通过在当前 issue 登记您的使用情况，并分享您使用夜莺监控的经验，将会自动进入 END USERS 列表，并获得社区的 VIP Support。

示例

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

We should add a metric to track the reason why a query results is not cached, and ensure we have another metric with the total number of queries for which we've the check to compare with.

https://github.com/grafana/mimir/blob/321e66db90cf39e8eb1067aada9064d15cac4ba9/pkg/frontend/querymiddleware/results_cache.go#L176-L194

_Originally posted by @pracucci in https://github.com/grafana/mimir/iss

Description

Some common traits don't bound by Send + Sync in definition but are required (every place) where they are used, like WalManager.

Proposal

<

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