←back to thread

264 points davidgomes | 5 comments | | HN request time: 0s | source
Show context
paulryanrogers ◴[] No.41875055[source]
Upgrades are hard. There was no replication in the before times. The original block-level replication didn't work among different major versions. Slony was a painful workaround based on triggers that amplified writes.

Newer PostgreSQL versions are better. Yet still not quite as robust or easy as MySQL.

At a certain scale even MySQL upgrades can be painful. At least when you cannot spare more than a few minutes of downtime.

replies(7): >>41875126 #>>41876174 #>>41876232 #>>41876375 #>>41877029 #>>41877268 #>>41877959 #
slotrans ◴[] No.41876232[source]
"Not as robust as MySQL"? Surely you're joking.
replies(3): >>41876309 #>>41876384 #>>41877139 #
1. Propelloni ◴[] No.41877139[source]
It is hard to live down a reputation ;)

MySQL was immortalized as the database in every LAMP stack. And just like PHP it improved considerably since then.

replies(1): >>41877303 #
2. p_l ◴[] No.41877303[source]
Also for licensing reasons for a long time there was surviving contingent of MySQL 3.23 in LAMP hosting.
replies(1): >>41878895 #
3. johannes1234321 ◴[] No.41878895[source]
While that change from LGPL to GPL affected only the client library (server always was GPL(+commercial)) and the MySQL company relatively quickly reacted with a FOSS exception to the GPL and by providing a reimplementation of the client library under PHP license (mysqlnd) to serve that market.

(I joined MySQL shortly after that mess, before the Sun acquisition)

replies(1): >>41880610 #
4. p_l ◴[] No.41880610{3}[source]
Random hosting providers that were major place for having your baby steps on LAMP stack didn't necessarily grok licensing much
replies(1): >>41884281 #
5. johannes1234321 ◴[] No.41884281{4}[source]
They also didn't like updating software - to likely that update to PHP or MySQL or something broke some bad script by a customer, who'd complain to the host.