| From: | Martín Marqués <martin(at)2ndquadrant(dot)com> |
|---|---|
| To: | "Gunnar \"Nick\" Bluth" <gunnar(dot)bluth(dot)extern(at)elster(dot)de>, pgsql-advocacy(at)postgresql(dot)org |
| Subject: | Re: Is Oracle using Gitlab Failure against PostgreSQL? |
| Date: | 2017-02-10 11:22:51 |
| Message-ID: | b0127fa6-9c32-64f7-bcb3-ac42b266e105@2ndquadrant.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-advocacy |
El 10/02/17 a las 05:01, Gunnar "Nick" Bluth escribió:
>
>> Question is, is there anything Postgres can really learn from this failure?
>
> Maybe re-order the docs? From what they made public, it seemed they
> either started backing up with a 7.x or early 8.x release and never
> adjusted the procedure to the new possibilities (LVM snapshots?!?
> Really?!?) or they stopped reading too early... :/
Simon Riggs wrote a nice blog after the incident, which IMO details the
flaws in the incident, with the conclusion that postgres wasn't in fault
there.
http://blog.2ndquadrant.com/dataloss-at-gitlab/
I don't think the issue they had has anything to do with how the
documentation is organized. This was just bad system administration
policies (you can see a bunch of changes they did after the incident
which aim at preventing from happening again).
In particular, the same problem would have happened with any database
engine, including Oracle. (I'm taking about the administrator deleting
all the data files)
Regards,
--
Martín Marqués http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Wei Shan | 2017-02-10 11:24:53 | Re: Is Oracle using Gitlab Failure against PostgreSQL? |
| Previous Message | Gunnar "Nick" Bluth | 2017-02-10 08:01:10 | Re: [PG-Advocacy] Is Oracle using Gitlab Failure against PostgreSQL? |