themachinestops@lemmy.dbzer0.com to Technology@lemmy.worldEnglish · 2 days agoVMware perpetual license holders receive cease-and-desist letters from Broadcomarstechnica.comexternal-linkmessage-square136linkfedilinkarrow-up1627arrow-down15cross-posted to: technology@lemmit.online
arrow-up1622arrow-down1external-linkVMware perpetual license holders receive cease-and-desist letters from Broadcomarstechnica.comthemachinestops@lemmy.dbzer0.com to Technology@lemmy.worldEnglish · 2 days agomessage-square136linkfedilinkcross-posted to: technology@lemmit.online
minus-squarepyr0ball@lemmy.dbzer0.comlinkfedilinkEnglisharrow-up10·2 days agoHow is it less problematic? I’ve only ever worked with the other two
minus-squarerottingleaf@lemmy.worldlinkfedilinkEnglisharrow-up3·1 day agoWell, compare setting up replication under Oracle and PGSQL.
minus-squareNinjasftw@lemmy.worldlinkfedilinkEnglisharrow-up2·11 hours agoReplication with postgres is really simple. Combine it with patroni and it’s so much better than oracle
minus-squarerottingleaf@lemmy.worldlinkfedilinkEnglisharrow-up1·1 hour agoOh, I’m not a DBA, so a stupid question - how do you avoid PGSQL replication breaking on full vacuum of a table? With patroni, shmatroni, macaroni, whatever.
How is it less problematic? I’ve only ever worked with the other two
Well, compare setting up replication under Oracle and PGSQL.
Replication with postgres is really simple. Combine it with patroni and it’s so much better than oracle
Oh, I’m not a DBA, so a stupid question - how do you avoid PGSQL replication breaking on full vacuum of a table? With patroni, shmatroni, macaroni, whatever.