[BUG]apecloud-postgresql pod crash after create

[ahjing99]

➜ ~ kbcli version
Kubernetes: v1.27.8-gke.1067004
KubeBlocks: 0.9.0-alpha.7
kbcli: 0.9.0-alpha.1

  `helm repo add kubeblocks-addons  https://jihulab.com/api/v4/projects/150246/packages/helm/stable`

"kubeblocks-addons" has been added to your repositories

      `helm repo update kubeblocks-addons `

Hang tight while we grab the latest from your chart repositories...
...Successfully got an update from the "kubeblocks-addons" chart repository
Update Complete. ⎈Happy Helming!⎈

      `helm upgrade --install apecloud-postgresql kubeblocks-addons/apecloud-postgresql --version 0.8.0-alpha.5 `

Release "apecloud-postgresql" does not exist. Installing it now.
W0328 14:09:42.151211   67705 warnings.go:70] The ClusterVersion CRD has been deprecated since 0.9.0
W0328 14:09:43.234786   67705 warnings.go:70] Due to the lack of practical use cases, this API is deprecated from KB 0.9.0.
W0328 14:09:49.607281   67705 warnings.go:70] The ClusterVersion CRD has been deprecated since 0.9.0
W0328 14:09:49.989215   67705 warnings.go:70] Due to the lack of practical use cases, this API is deprecated from KB 0.9.0.
NAME: apecloud-postgresql
LAST DEPLOYED: Thu Mar 28 14:09:27 2024
NAMESPACE: default
STATUS: deployed
REVISION: 1
TEST SUITE: None

 `kbcli cluster create  apepg-gbaqtd --termination-policy=Delete --monitoring-interval=0 --cluster-definition=apecloud-postgresql --enable-all-logs=false --cluster-version=ac-postgresql-latest --set cpu=100m,memory=0.5Gi,replicas=3,storage=1Gi  --namespace default `

Cluster apepg-gbaqtd created

➜  ~ k get pod | grep pg
apepg-gbaqtd-postgresql-0      2/2     Running            1 (15m ago)     16m
apepg-gbaqtd-postgresql-1      1/2     CrashLoopBackOff   7 (4m23s ago)   16m
apepg-gbaqtd-postgresql-2      1/2     CrashLoopBackOff   7 (4m17s ago)   16m

➜  ~ k logs apepg-gbaqtd-postgresql-1
Defaulted container "postgresql" out of: postgresql, lorry, init-permissions (init)
apepg-gbaqtd-postgresql-0.apepg-gbaqtd-postgresql-headless:5432 - accepting connections
initdb: invalid option -- 'i'
Try "initdb --help" for more information.
➜  ~ k logs apepg-gbaqtd-postgresql-2
Defaulted container "postgresql" out of: postgresql, lorry, init-permissions (init)
apepg-gbaqtd-postgresql-0.apepg-gbaqtd-postgresql-headless:5432 - accepting connections
initdb: invalid option -- 'i'
Try "initdb --help" for more information.
➜  ~ k logs apepg-gbaqtd-postgresql-0
Defaulted container "postgresql" out of: postgresql, lorry, init-permissions (init)
have been initialized
2024-03-28 06:11:23.182 UTC [7] LOG:  starting PostgreSQL 14.10 (with consensus 0.7.1 PGTAG=CONSENSUS_HOOK_2_1_0_PG_14_10) on x86_64-pc-linux-gnu, compiled by gcc (Debian 10.2.1-6) 10.2.1 20210110, 64-bit
2024-03-28 06:11:23.183 UTC [7] LOG:  listening on IPv4 address "0.0.0.0", port 5432
2024-03-28 06:11:23.183 UTC [7] LOG:  listening on IPv6 address "::", port 5432
2024-03-28 06:11:23.187 UTC [7] LOG:  listening on Unix socket "/var/run/postgresql/.s.PGSQL.5432"
2024-03-28 06:11:23.192 UTC [8] LOG:  database system was shut down at 2024-03-28 06:11:18 UTC
2024-03-28 06:11:23.282 UTC [7] LOG:  database system is ready to accept connections