public inbox for [email protected]  

help / color / mirror / Atom feed

From: Gregory Stark <[email protected]>
To: Tom Lane <[email protected]>
Cc: Zubkovsky, Sergey <[email protected]>
Cc: [email protected]
Subject: Re: [DOCS] pg_total_relation_size() and CHECKPOINT
Date: Fri, 14 Mar 2008 18:30:24 +0000
Message-ID: <[email protected]> (raw)
In-Reply-To: <[email protected]>
References: <[email protected]>
	<[email protected]>

"Tom Lane" <[email protected]> writes:

> "Zubkovsky, Sergey" <[email protected]> writes:
>> The previous results were received on PG 8.3 version:
>> 	"PostgreSQL 8.3.0, compiled by Visual C++ build 1400"
>
> Hmm.  I find the whole thing fairly worrisome, because what it suggests
> is that Windows isn't actually allocating file space during smgrextend,
> which would mean that we'd be prone to running out of disk space at
> unfortunate times --- like during a checkpoint, after we've already
> promised the client the data is committed.

Surely we can't lose after the fsync? Losing at commit rather than at the time
of insert might still be poor, but how could we lose after we've promised the
data is committed?

-- 
  Gregory Stark
  EnterpriseDB          http://www.enterprisedb.com
  Ask me about EnterpriseDB's Slony Replication support!

view thread (24+ messages)  latest in thread

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: [email protected]
  Cc: [email protected], [email protected], [email protected], [email protected]
  Subject: Re: [DOCS] pg_total_relation_size() and CHECKPOINT
  In-Reply-To: <[email protected]>

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

This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox