Priority of toml config vs env vars for connection pool size

Do you want to request a feature or report a bug?

Neither

What is the current behavior?

It seems that setting the size of a connection pool with the config file takes precedence over using STORE_CONNECTION_POOL_SIZE.

If the current behavior is a bug, please provide the steps to reproduce and if possible a minimal demo of the problem.

Start a graph node which uses

[store]
[store.primary]
connection = "<%= pgString %>"
pool_size = [
{ node = ".*", size = 30 },
]

and start the node with STORE_CONNECTION_POOL_SIZE=50. Then check the pool size using graphman and see that the config takes precedence.

What is the expected behavior?

I would expect the env var to take precedence over the config. Though I understand the env var isn't as fine grained.

Maybe I'm misunderstanding what STORE_CONNECTION_POOL_SIZE is meant for relative to pool_size in [store]?

TOML の [store.primary] にある pool_size 設定と STORE_CONNECTION_POOL_SIZE=50 を使って設定を再現し、その後 graphman で結果のプールサイズを確認します。細粒度の pool_size 設定と環境変数の間で意図されている優先順位を判断し、対象を絞ったテストまたは文書化した結果で選択した動作を検証します。