Re: Hard limit on WAL space used (because PANIC sucks)
От | Jaime Casanova |
---|---|
Тема | Re: Hard limit on WAL space used (because PANIC sucks) |
Дата | |
Msg-id | CAJKUy5hwNUKWeYseZau-JUJ09zjPC8AnLmpj+jd0c8ykciHg7A@mail.gmail.com обсуждение исходный текст |
Ответ на | Re: Hard limit on WAL space used (because PANIC sucks) (Christian Ullrich <chris@chrullrich.net>) |
Список | pgsql-hackers |
On Thu, Jun 6, 2013 at 4:28 PM, Christian Ullrich <chris@chrullrich.net> wrote: > * Heikki Linnakangas wrote: > >> The current situation is that if you run out of disk space while writing >> WAL, you get a PANIC, and the server shuts down. That's awful. We can > > >> So we need to somehow stop new WAL insertions from happening, before >> it's too late. > > >> A naive idea is to check if there's enough preallocated WAL space, just >> before inserting the WAL record. However, it's too late to check that in > > > There is a database engine, Microsoft's "Jet Blue" aka the Extensible > Storage Engine, that just keeps some preallocated log files around, > specifically so it can get consistent and halt cleanly if it runs out of > disk space. > fwiw, informix (at least until IDS 2000, not sure after that) had the same thing. only this was a parameter to set, and bad things happened if you forgot about it :D -- Jaime Casanova www.2ndQuadrant.com Professional PostgreSQL: Soporte 24x7 y capacitación Phone: +593 4 5107566 Cell: +593 987171157
В списке pgsql-hackers по дате отправления: