Immediate subscriber updating
Switching is possible between variations of a Variable Subscription product, or Simple Subscriptions within a Grouped product, depending on the settings you choose.
It is also possible to change quantities on a product using the switching process.
I want to know if in a transactional push replication with updatable subscribers, a commit is only done when all subscribers have succeeded to make it, or if it only guarantees the correct commit in the publisher and the subscriber that generated the change in the database.
I've found this in msdn, but I don't know if the two-phase commit protocol is referring to all instances (publisher and subscribers, or just one subscriber and the publisher) When data is updated at a Subscriber, it is first propagated to the Publisher and then propagated to other Subscribers.
To learn about creating and updating subscriptions, see Managing Topics and Subscriptions.
Google Cloud Pub/Sub delivers each published message at least once for every subscription.
This is also the case with limiting the time of day you send.
The changes will be sent to the other subscribers in due course.If you have a question not answered here, you may find answers in the Subscriptions FAQ.