Conversation

You’re unable to view this Tweet because this account owner limits who can view their Tweets. Learn more
You’re unable to view this Tweet because this account owner limits who can view their Tweets. Learn more
Replying to
I agree we should do more to make upgrades less disruptive / painful, but I very much doubt integrating pgbouncer + Slony is the answer. It has downsides too, making it impractical for plenty of valid cases. Our philosophy generally is to build infrastructure for external tools.
1
1
You’re unable to view this Tweet because this account owner limits who can view their Tweets. Learn more
You’re unable to view this Tweet because this account owner limits who can view their Tweets. Learn more
You’re unable to view this Tweet because this account owner limits who can view their Tweets. Learn more
You’re unable to view this Tweet because this account owner limits who can view their Tweets. Learn more
Replying to
1/2 I'm not against that in principle, of course, it's roughly what happened with physical (and logical) replication IIRC. Infrastructure, API, built-in tool seems reasonable. But TBH I'm somewhat annoyed when people complain the "community" did not do something.
2
Replying to and
2/2 Devs pick stuff based on cost/benefit, more or less. So either they have better things to work on (more likely to succeed, more benefit for their customers, ...). Can't blame them 🤷‍♂️ Best way to fix something you consider valuable is to start working on it, commit $/time/...
2