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

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.

Start by tracing how standby replication from a remote standalone PostgreSQL source handles the preparedDatabase and defaultUsers settings. Compare the resulting cluster state with the requested configuration, and determine whether creating the database and users is expected after replication; capture the behavior in a focused test or documentation update.