Can I use a database for my state storage in the helm chart?

Based on the information provided in the extracts, it seems that the Helm chart for Airbyte currently supports Minio, S3, and GCS for state storage. There is no explicit mention of using a database for state storage in the Helm chart. However, Airbyte does use a database (Postgres) to store internal state and metadata. This can be managed in two ways: using the default Postgres database that Airbyte spins up as part of the Docker service, or through a dedicated custom Postgres instance. This is not the same as state storage, but it's worth noting that Airbyte does use a database for some of its internal operations. If you're looking to use a database for state storage, it might be worth raising this as a feature request on the Airbyte GitHub or discussion forum. Sources: - [Forum Post > Most recent helm chart has broken state storage for non-minio](https://discuss.airbyte.io/t/3814) - [Documentation > Operator-guides > Configuring the Airbyte Database](https://docs.airbyte.com/operator-guides/configuring-airbyte-db/)

Are you able to interpret errors from stack traces?