Re: Is Oracle using Gitlab Failure against PostgreSQL?

Wei Shan <[email protected]>
Newsgroups gmane.comp.db.postgresql.advocacy
Message-ID <CAFe9ZToMPtTgZmz6PSj5h9OdFe2XTMgx30eExcnyoKDPj3FwQw@mail.gmail.com>
Funny enough, the admin of the group, who was the thread starter, closed
the thread after his final response.

On 10 February 2017 at 11:22, Martín Marqués <[email protected]> wrote:

> 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
>
>
> --
> Sent via pgsql-advocacy mailing list ([email protected])
> To make changes to your subscription:
> http://www.postgresql.org/mailpref/pgsql-advocacy
>



-- 
Regards,
Ang Wei Shan
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.