←back to thread

264 points davidgomes | 1 comments | | HN request time: 0s | source
Show context
elric ◴[] No.41876822[source]
Lots of dogmatism in this discussion, it seems. A couple of things:

1. Most psql deployments are not exposed to the interwebz, they are typically only accessible to the applications that need them by virtue of network setup (firewalls etc). This limits the attack vector to whatever the application does. Good.

2. Distro vendors (RHEL et al) often stick to major psql release for the lifecycle of the OS version. If the OS lives longer than the psql major version, they take on the responsability of backporting critical security issues.

3. While upgrades aren't hard, they're not easy either.

4. Psql is pretty much feature complete for many workloads, and pretty stable in general. For many people, there is little need to chase the latest major version.

replies(7): >>41876901 #>>41877104 #>>41877174 #>>41877411 #>>41877438 #>>41878003 #>>41879089 #
atoav ◴[] No.41877104[source]
Also:

5. If your IT department is spread thin already and that old version is running fine, the incentive to potentially create more work for yourself is not gigantic.

replies(1): >>41877167 #
Dalewyn ◴[] No.41877167[source]
One of the first laws of the universe that a good engineer learns is: Do not fix what is not broken.

And no, being old is not broken.

replies(9): >>41877567 #>>41877619 #>>41877848 #>>41877998 #>>41878067 #>>41878190 #>>41879176 #>>41880524 #>>41880526 #
1. vbezhenar ◴[] No.41877848{3}[source]
It leads to a lot of old software which is not going to be upgraded ever. Then the entire project dies and gets rewritten from the scratch, because nobody wants to work with Windows 2003 server running Delphi 7, Java 1.4 and Oracle 9i in 2020 (personal experience).

Old software is not necessarily broken, but it is always a tech debt. And you can't live in debt forever, our IT does not work this way.