|From:||Stephen Frost <sfrost(at)snowman(dot)net>|
|To:||Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at>|
|Cc:||Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com>, David Steele <david(at)pgmasters(dot)net>, Robert Haas <robertmhaas(at)gmail(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>|
|Subject:||Re: Remove Deprecated Exclusive Backup Mode|
|Views:||Raw Message | Whole Thread | Download mbox|
* Laurenz Albe (laurenz(dot)albe(at)cybertec(dot)at) wrote:
> Stephen Frost wrote:
> > * Peter Eisentraut (peter(dot)eisentraut(at)2ndquadrant(dot)com) wrote:
> > > Clearly, not having to do that at all is better, but if this is all
> > > there is to it, then I'm confused by the characterizations of how awful
> > > and terrible this feature is and how we must rush to remove it.
> > It's not all there is to it though.
> > This issue leads to extended downtime regularly and is definitely a huge
> > 'gotcha' for users, even if you don't want to call it outright broken,
> Only if PostgreSQL crashes regularly, right?
This happens anytime a backup is in progress and the system crashes in
any way- PostgreSQL going down, the container Postgres is running in,
the server Postgres is running on, or if the filesystem that Postgres is
running on goes away, etc.
There's certainly no shortage of cases where this can happen.
|Next Message||Pavel Stehule||2019-01-10 15:15:18||Re: PostgreSQL vs SQL/XML Standards|
|Previous Message||Laurenz Albe||2019-01-10 14:56:41||Re: Remove Deprecated Exclusive Backup Mode|