News for hackers. Stuff that matters.
Re:Thoughts on PostgreSQL in 2024 by subarctic on Tuesday January 02, 2024 @08:04PM (#38849403)
Doesn't 1 second of database downtime just mean that a ticket that is scanned during that 1 second window will take 1.5-2 seconds to scan instead of, say, 500ms? Why would that result in 10 minutes of troubleshooting?
Re:Thoughts on PostgreSQL in 2024 by abhibeckert on Tuesday January 02, 2024 @08:20PM (#38849532)
Because when it doesn't work, they'll get an error message, and then they will try to figure out how to fix the error message.

These aren't tech savvy people. You don't hire an IT person to stand at a door scanning a thousand QR codes for 20 minutes three nights a week.

Re:Thoughts on PostgreSQL in 2024 by ses1984 on Tuesday January 02, 2024 @10:19PM (#38850282)
Why would you immediately show an error message instead of some kind of background retry?

Or at the very least the message should tell the operator to retry.

Re:Thoughts on PostgreSQL in 2024 by emeril on Wednesday January 03, 2024 @08:30AM (#38853812)
it isn't downtime he's as concerned about as it's about speed

he could build in behavior to retry/wait for several seconds before erroring out but his selling point is speed seemingly (with little risk of sale negatives/positives/theft)

Re:Thoughts on PostgreSQL in 2024 by jtc331 on Wednesday January 03, 2024 @08:36AM (#38853872)
That doesn’t have to incur actual downtime if you use pgbouncer in front of Postgres and pause the pool.