You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The documentation mentions that the replica pod for the database is read-only. However, when inspecting the pod, it shows that the readOnly flag is set to false.
Volumes:
pgdata:
Type: PersistentVolumeClaim (a reference to a PersistentVolumeClaim in the same namespace)
ClaimName: pgcluster-pvc
ReadOnly: false
Would it make sense to also set the volume bind-mount to readOnly for the pod container or would that break the normal DB operation ?
The text was updated successfully, but these errors were encountered:
with the replica being able to be promoted to a read-write master (recovery) it would need to be set to read/write, so essentially doing it this way supports a future 'failover' command, it will work sort of like this: "pgo failover mycluster', when a user enters that command it will find a replica and trigger the failover to it plus a whole lot of other stuff :^)) hope that helps.
The documentation mentions that the replica pod for the database is read-only. However, when inspecting the pod, it shows that the readOnly flag is set to
false
.Would it make sense to also set the volume bind-mount to readOnly for the pod container or would that break the normal DB operation ?
The text was updated successfully, but these errors were encountered: