4 ms·
Out of curiosity, why can’t you change the behavior that prevents you from doing rollbacks? This design seems rather brittle. What happens if a node spontaneou
by otterley 3mo ago
Out of curiosity, why can’t you change the behavior that prevents you from doing rollbacks?
This design seems rather brittle. What happens if a node spontaneously fails, or you need to move to another AZ? (Assuming you’re in the cloud.)
- conradludgate 3mo agoThe design is postgres. It's our customers that do stateful things on those connections. Unfortunately it's tools like pgdump/pgrestore that are not tolerant to connection interruption. Node failure is indeed a problem. Not much we can do there. Fortunately it's rare enough historically. We are working to split the code so that the process that holds tcp connections isn't the process that handles the logic though, so it's easier to update inplace
- otterley 3mo agoWhat does it mean to do “stateful things on a connection”? Feel free to point me to literature if you’d be repeating something already written or well known.