4 ms·
Frankly these new-fangled auto-everything databases are untrustworthy I'm not asking for postgres to change its ways and become "untrustworthy". I'm merely as
by moe 12y ago
Frankly these new-fangled auto-everything databases are untrustworthy
I'm not asking for postgres to change its ways and become "untrustworthy".
I'm merely asking that postgres wraps more automation and convenience around the things that it already does.
Replication should generally be operated from inside psql. Spinning up a slave should be a single command. Failing over should be a single command. There should be meaningful error messages, ETAs and progress bars. No rsync'ing of WAL files, no futzing with config files. No elaborate third party 'repmgr' daemons.
- pyvpx 12y ago> I'm merely asking that postgres wraps more automation and convenience around the things that it already does. and if history is any indication, it will when it's good and ready to be convenient and automated. as a previous poster (or two) most eloquently noted, postgres tends to work from the bottom up. when the "fundamentals" have been hashed out and thoroughly tested through all or nearly all edge cases, then convenient interfaces "bubble up" and hey, your patches are always welcomed :)
- moe 12y agoand if history is any indication, it will Very true. I was merely bemoaning the status quo. This is a thread about a third party tool to patch up a rather severe UX flaw after all...