pg.ddx.io pgsql-admin@postgresql.org mailing list archivehelp / color / mirror / Atom feed
SQLSTATE 53100 could not extend file / disk full 2+ messages / 2 participants [nested] [flat]
* SQLSTATE 53100 could not extend file / disk full @ 2012-05-07 12:03 Jan-Peter Seifert <Jan-Peter.Seifert@gmx.de> 2012-05-07 17:09 ` Re: SQLSTATE 53100 could not extend file / disk full Kevin Grittner <Kevin.Grittner@wicourts.gov> 0 siblings, 1 reply; 2+ messages in thread From: Jan-Peter Seifert @ 2012-05-07 12:03 UTC (permalink / raw) To: pgsql-admin Hello, I wonder whether extra measures are necessary to recover from a disk full error besides freeing enough disk space? It seems that there are enough security measures: http://archives.postgresql.org/message-id/CAHHcrepQNCN3HoXSWAOtsj3HJKp5NoepB2ky3dFgVA4JCXh-Qw@mail.g... Is it no problem if the WAL is within the same disk space and can't be written as well? I didn't see anything in the FAQ: http://wiki.postgresql.org/wiki/FAQ Should you free enough disk space, do a checkpoint, restart the server and check the server log? Thank you very much, Peter -- Empfehlen Sie GMX DSL Ihren Freunden und Bekannten und wir belohnen Sie mit bis zu 50,- Euro! https://freundschaftswerbung.gmx.de ^ permalink raw reply [nested|flat] 2+ messages in thread
* Re: SQLSTATE 53100 could not extend file / disk full 2012-05-07 12:03 SQLSTATE 53100 could not extend file / disk full Jan-Peter Seifert <Jan-Peter.Seifert@gmx.de> @ 2012-05-07 17:09 ` Kevin Grittner <Kevin.Grittner@wicourts.gov> 0 siblings, 0 replies; 2+ messages in thread From: Kevin Grittner @ 2012-05-07 17:09 UTC (permalink / raw) To: Jan-Peter Seifert <Jan-Peter.Seifert@gmx.de>; pgsql-admin "Jan-Peter Seifert" <Jan-Peter.Seifert@gmx.de> wrote: > I wonder whether extra measures are necessary to recover from a > disk full error besides freeing enough disk space? > Is it no problem if the WAL is within the same disk space and > can't be written as well? > Should you free enough disk space, do a checkpoint, restart the > server and check the server log? At our shop, we have rarely run out of disk space on a production machine, due to close monitoring; but in those few cases, and in the somewhat more frequent case that it happened in a development environment, we have simply freed space and continued. From what I have seen, the PostgreSQL development community tries very hard to ensure that you can do this safely. On the other hand, it would obviously be very hard to thoroughly test every possible code path under such conditions, so I always try to watch for possible problems afterward. -Kevin ^ permalink raw reply [nested|flat] 2+ messages in thread
end of thread, other threads:[~2012-05-07 17:09 UTC | newest] Thread overview: 2+ messages (download: mbox mbox.gz follow: Atom feed) -- links below jump to the message on this page -- 2012-05-07 12:03 SQLSTATE 53100 could not extend file / disk full Jan-Peter Seifert <Jan-Peter.Seifert@gmx.de> 2012-05-07 17:09 ` Kevin Grittner <Kevin.Grittner@wicourts.gov>
This inbox is served by DDX for PostgreSQL; see mirroring instructions for how to clone and mirror all data and code used for this inbox