"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! -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
