4
If “Google SQL” allows that, you can set max_standby_streaming_delay
to -1
so that replication is delayed if a conflict is detected.
Then the query will not be canceled, but replication may lag if applying changes would cause a conflict.
Consider getting an “unfettered” PostgreSQL.
3
If you would like set hot_standby_feedback = on
, I’ll suggest that you indicate your interest in the open feature request on Google Cloud Platform’s Public Issue Tracker tool. That way someone can look into the handling query conflict issues your Cloud SQL PostgreSQL instance encountered.
I’ve also been monitoring an open thread in the Issue Tracker about making max_standby_archive_delay
and max_standby_streaming_delay
flags available to users to set. You can track it there as well. Hope this helps!
- [Django]-Django static files not loading
- [Django]-Class attribute inheritance in Django models
- [Django]-Counting distinct elements in Django ArrayField