3 ms·

So postgresql upgrades are a piece of cake if your users doesn't care if your system is available to them. Is this some paradoy of the older claim that MongoDb

So postgresql upgrades are a piece of cake if your users doesn't care if your system is available to them. Is this some paradoy of the older claim that MongoDb is a great system if your user doesn't care if their data is lost?

Avamander 4y ago
Do you actually have such an uptime requirement or do you think you have such an uptime requirement? How are you conducting it with other databases?
- wutwutwutwut 4y ago
  Yes, if the software I work on doesn't work for 5 minutes we have a ton of tickets from customer. We have tens of thousands of customers who pay for it. Not being able to shut down your system for an hour isn't exactly a unique requirement. Technically our SLA is 10 minutes to perform jobs but our customers don't wait that long before creating tickets. We pay Microsoft to perform upgrades transparently for us. They have multiple servers and they shuffle transaction logs and traffic between them to ensure availability during outages and upgrades. There are 6 copies of each database in different regions. Not sure how that is relevant, though?
  - mrelectric 4y ago
    It is relevant, reread and understand the parent comment. Get a managed pg and you'll have the same thing.
    - wutwutwutwut 4y ago
      I believe you are the one who need to reread the thread. The person I replied to claimed that "Postgresql upgrades are a piece of cake." But it is not. It's complex to do properly, just like with most if not all other databases. Claiming that it is easy as is just ignorant and spreading such misinformation is bad.
      - mrelectric 4y ago
        I never claimed it's easy, I just said get a managed pg, offload it to someone else and then it's easy yeah. I'm wondering the same as other commentator above me, what's the difference in other unmanaged dbs?
    - rmbyrro 4y ago
      That's the point. It's not a weakness in Postgres. Managing upgrades in a highly available, close to 100% uptime database is hard. If you want piece of cake, outsource this service and be happy enjoying the database features working as you please.
      - mrelectric 4y ago
        Yes, that's what I was saying :)
minusf 4y ago
even four 9's give 50 minutes a year to do maintenance work. i am a fan of planning for maintenance. planned downtime is definitely accepted by most of the population. i mean what you gonna do? much better a planned downtime than an outage. leaving a system to rot just because the architecture is "don't touch it while it's working" is a sure recipe for a disaster of some kind.
- wutwutwutwut 4y ago
  > even four 9's give 50 minutes a year to do maintenance work. Just the security patching of the host OS will likely consume a bunch of those minutes. Not sure what point you were trying to make apart from that. I am not advocating that people should leave system to rot.

Avamander 4y ago

Do you actually have such an uptime requirement or do you think you have such an uptime requirement? How are you conducting it with other databases?

wutwutwutwut 4y ago
Yes, if the software I work on doesn't work for 5 minutes we have a ton of tickets from customer. We have tens of thousands of customers who pay for it. Not being able to shut down your system for an hour isn't exactly a unique requirement. Technically our SLA is 10 minutes to perform jobs but our customers don't wait that long before creating tickets. We pay Microsoft to perform upgrades transparently for us. They have multiple servers and they shuffle transaction logs and traffic between them to ensure availability during outages and upgrades. There are 6 copies of each database in different regions. Not sure how that is relevant, though?
- mrelectric 4y ago
  It is relevant, reread and understand the parent comment. Get a managed pg and you'll have the same thing.
  - wutwutwutwut 4y ago
    I believe you are the one who need to reread the thread. The person I replied to claimed that "Postgresql upgrades are a piece of cake." But it is not. It's complex to do properly, just like with most if not all other databases. Claiming that it is easy as is just ignorant and spreading such misinformation is bad.
    - mrelectric 4y ago
      I never claimed it's easy, I just said get a managed pg, offload it to someone else and then it's easy yeah. I'm wondering the same as other commentator above me, what's the difference in other unmanaged dbs?
  - rmbyrro 4y ago
    That's the point. It's not a weakness in Postgres. Managing upgrades in a highly available, close to 100% uptime database is hard. If you want piece of cake, outsource this service and be happy enjoying the database features working as you please.
    - mrelectric 4y ago
      Yes, that's what I was saying :)

minusf 4y ago

even four 9's give 50 minutes a year to do maintenance work. i am a fan of planning for maintenance. planned downtime is definitely accepted by most of the population. i mean what you gonna do? much better a planned downtime than an outage. leaving a system to rot just because the architecture is "don't touch it while it's working" is a sure recipe for a disaster of some kind.

wutwutwutwut 4y ago
> even four 9's give 50 minutes a year to do maintenance work. Just the security patching of the host OS will likely consume a bunch of those minutes. Not sure what point you were trying to make apart from that. I am not advocating that people should leave system to rot.