Josh Baird
Josh Baird
This is still an issue in 1911.4.0 as far as I can tell.
Hi @petere - thanks for responding! No other software running, although this is Amazon RDS. But, this is the first time I have ever seen this happen, and also the...
Thanks @eulerto and @martinmarques. Correct, we can't use the basebackup option, so I guess we're stuck with having pglogical sync the data for us either using `data_synchonize=true` or `data_synchronize=false` and...
@gilesw Not sure if this will help, but you can also use `pglogical.wait_for_subscription_sync_complete(sub_name)` which will block until the initial sync is complete. I don't think this helps your ordering challenge,...
Hi @luss! We met in NYC a few years ago at an AWS event when the RDS Postgres Customer Advisory Board was established. Yes - we are rehearsing the upgrade...
In my testing, it seems like pglogical isn't aware of where it needs to be begin replicating when you pre-seed data (using the snapshot method referenced above). It looks like...
I overcame some of my issues with taking a slightly different approach: * After importing the schema into the `subscriber` - drop all of the foreign key constraints. This will...
@midhunkrishnakv I'm having this exact same issue. Did you ever figure it out?
You probably have a CMP problem that is returning no data thus making Argo want to remove all resources. Check the repo-server logs for more details.
@nikola-jokic I just came across this and I'm wondering why GitHub can't just provide the CRDs outside of the helm chart so that users can 1) update CRDs manually using...