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
Hello Pgpool-II community,
I have a PostgreSQL cluster with 3 nodes (xxxxxl01, xxxxxl02, xxxxxl03) and Pgpool-II. The PostgreSQL data directory is located on a remote instance per company policy.
On the 29th of this month, an incident occurred where the "data" directory disappeared on all 3 nodes simultaneously without apparent cause. It's the third time it's happened. We suspect it may have been caused by a problem on the remote instance hosting the data directories.
Is it possible that a failure on the remote instance could cause the PostgreSQL data directories on all 3 nodes to disappear or be deleted at the same time?
Any suggestions on how to prevent these types of incidents or Pgpool-II and PostgreSQL configuration best practices to avoid data loss in scenarios like this?
I appreciate in advance any guidance or advice you can provide. Greetings.
The text was updated successfully, but these errors were encountered:
Hello Pgpool-II community,
I have a PostgreSQL cluster with 3 nodes (xxxxxl01, xxxxxl02, xxxxxl03) and Pgpool-II. The PostgreSQL data directory is located on a remote instance per company policy.
On the 29th of this month, an incident occurred where the "data" directory disappeared on all 3 nodes simultaneously without apparent cause. It's the third time it's happened. We suspect it may have been caused by a problem on the remote instance hosting the data directories.
Is it possible that a failure on the remote instance could cause the PostgreSQL data directories on all 3 nodes to disappear or be deleted at the same time?
Any suggestions on how to prevent these types of incidents or Pgpool-II and PostgreSQL configuration best practices to avoid data loss in scenarios like this?
I appreciate in advance any guidance or advice you can provide. Greetings.
The text was updated successfully, but these errors were encountered: