pg.ddx.io  pgsql-performance@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Kevin Grittner <Kevin.Grittner@wicourts.gov>
Cc: Jeremy Haile <jhaile@fastmail.fm>
Cc: pgsql-performance@postgresql.org
Subject: Re: URGENT: Out of disk space pg_xlog
Date: Fri, 22 Dec 2006 13:46:10 -0500
Message-ID: <26666.1166813170@sss.pgh.pa.us> (raw)
In-Reply-To: <458BD182.EE98.0025.0@wicourts.gov>
References: <1166803606.2828.281701761@webmail.messagingengine.com>
	<1166806378.10592.281708161@webmail.messagingengine.com>
	<458BC058.EE98.0025.0@wicourts.gov>
	<458BC058.EE98.0025.0@wicourts.gov>
	<26238.1166811258@sss.pgh.pa.us>
	<458BD182.EE98.0025.0@wicourts.gov>

"Kevin Grittner" <Kevin.Grittner@wicourts.gov> writes:
> Tom Lane <tgl@sss.pgh.pa.us> wrote: 
>> before the system crash?  The scenario we've seen in the past is
>> 
>> * data partition out of space, so writes fail
>> * each time Postgres attempts a checkpoint, writes fail, so the
>> checkpoint fails.  No data loss at this point, the dirty buffers
>> just stay in memory.
>> * pg_xlog bloats because we can't truncate away old segments
 
> So, at this point, if space is freed on the data partition somehow,
> Postgres recovers with no problems?  (i.e.,, the database is still
> running and no requests have been terminated abnormally due to the space
> problems?)

Right, no committed transactions have been lost.  Depending on what you
are doing, you might see individual transactions fail due to
out-of-space --- an INSERT/UPDATE that couldn't find free space within
its table would probably fail while trying to extend the table, and
anything requiring a large temp file would fail.
 
> Just to confirm what I would assume at this point -- non-committed
> transactions should roll back cleanly; it is reasonable to assume no
> corruption at this point?

Yeah, I would expect no problems.

			regards, tom lane



view thread (20+ messages)  latest in thread

Message-ID: <26666.1166813170@sss.pgh.pa.us>
Permalink:  ../26666.1166813170@sss.pgh.pa.us/
Also on:    postgresql.org/message-id/26666.1166813170@sss.pgh.pa.us

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: pgsql-performance@postgresql.org
  Cc: tgl@sss.pgh.pa.us, Kevin.Grittner@wicourts.gov, jhaile@fastmail.fm
  Subject: Re: URGENT: Out of disk space pg_xlog
  In-Reply-To: <26666.1166813170@sss.pgh.pa.us>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

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