Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Operator doesn't create prepared databases after standby replication from standalone source #2846

Open
klefevre opened this issue Jan 17, 2025 · 0 comments

Comments

@klefevre
Copy link

Hello,

I’ve encountered an interesting situation where I "hacked" (is it?) the operator to use the standby feature for replicating a standalone PostgreSQL database located on a remote server into my Kubernetes cluster. The source database's tables were in the postgres database.

The replication worked so well that the operator didn’t perform some expected tasks, specifically:

  1. It didn’t create the database I specified in the preparedDatabase .
  2. It didn’t create any users, even though defaultUsers: true was set.

Now that my data was "backed up" within my cluster. Does anybody know if there a way to make the operator to actually create these default users and database?

I would appreciate any guidance or clarification on how the operator handles such scenarios. Let me know if you need more details about my setup.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant