Re: [DOCS] pg_total_relation_size() and CHECKPOINT - Mailing list pgsql-hackers

From Tom Lane
Subject Re: [DOCS] pg_total_relation_size() and CHECKPOINT
Date
Msg-id 21561.1205515308@sss.pgh.pa.us
Whole thread Raw
In response to Re: [DOCS] pg_total_relation_size() and CHECKPOINT  ("Zubkovsky, Sergey" <Sergey.Zubkovsky@transas.com>)
Responses Re: [DOCS] pg_total_relation_size() and CHECKPOINT  (Gregory Stark <stark@enterprisedb.com>)
List pgsql-hackers
"Zubkovsky, Sergey" <Sergey.Zubkovsky@transas.com> 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.

Can any Windows hackers look into this and find out what's really
happening?
        regards, tom lane


pgsql-hackers by date:

Previous
From: "Joshua D. Drake"
Date:
Subject: Commit fest?
Next
From: Alvaro Herrera
Date:
Subject: Re: PROC_VACUUM_FOR_WRAPAROUND doesn't work expectedly