fix(postgresql/guides) plan change process is restarting follower instances first#3745
Conversation
| When changing for a Business plan, the platform starts additional instances | ||
| with the targeted size. If necessary, it then reboots the previously existing |
There was a problem hiding this comment.
question:
When changing from a Starter plan to a Business one, we switch from a single-instance setup to a primary+follower setup, don't we?
So "additional instances" is the new "follower instance", and "previously existing instance" it the "primary" one, aren't they?
(if so, I don't get why this change)
There was a problem hiding this comment.
When changing from a Starter plan to a Business one, we switch from a single-instance setup to a primary+follower setup, don't we?
Yes correct
So "additional instances" is the new "follower instance", and "previously existing instance" it the "primary" one, aren't they?
To be more precise: "additional instances" are the new "follower instance(s)". This is the only little change that I wanted to bring. But from my first read the change was obvious, now it's not the case anymore 😅
it the "primary" one, aren't they?
Yes correct
So I'm suggesting a change: a24fdec, WDYT?
0ec03f0 to
abf956c
Compare
abf956c to
c0db29d
Compare
No description provided.