Re:Updating a 50 terabyte PostgreSQL database (2018)
by easton on Monday March 22, 2021 @09:16AM
(#26540335)
I wonder what the break even point is for just that one feature. 15 minutes of downtime per year, which you can schedule and maybe work around, or five-six figures to Oracle or Microsoft for them to already have solved this problem, but otherwise you don’t get much else (that you need).
[ Parent
| on HN ]
Re:Updating a 50 terabyte PostgreSQL database (2018)
by ComodoHacker on Monday March 22, 2021 @09:28AM
(#26540476)
It could be more than one downtime per year, if we take security patches into account.
Re:Updating a 50 terabyte PostgreSQL database (2018)
by darksaints on Monday March 22, 2021 @09:45AM
(#26540691)
Security patches are minor upgrades...the upgrades only cause significant downtime if there are large changes in on-disk representation, which shouldn't happen for a security patch.