From: Tom Lane <tgl@sss.pgh.pa.us>
To: Greg Stark <gsstark@mit.edu>
Cc: Pierre C <lists@peufeu.com>
Cc: Alvaro Herrera <alvherre@commandprompt.com>
Cc: Dave Crooke <dcrooke@gmail.com>
Cc: pgsql-performance@postgresql.org
Subject: Re: Block at a time ...
Date: Wed, 17 Mar 2010 10:27:04 -0400
Message-ID: <27894.1268836024@sss.pgh.pa.us> (raw)
In-Reply-To: <407d949e1003170252y72d223c3kcc18266140a60997@mail.gmail.com>
References: <ca24673e1003161658g6a0fa30dg2c158db395ac08@mail.gmail.com>
<20100317001405.GL3037@alvh.no-ip.org>
<op.u9pa7vzleorkce@localhost>
<407d949e1003170252y72d223c3kcc18266140a60997@mail.gmail.com>
Greg Stark <gsstark@mit.edu> writes:
> I think we need posix_fallocate().
The problem with posix_fallocate (other than questionable portability)
is that it doesn't appear to guarantee anything at all about what is in
the space it allocates. Worst case, we might find valid-looking
Postgres data there (eg, because a block was recycled from some recently
dropped table). If we have to write something anyway to zero the space,
what's the point?
regards, tom lane
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, gsstark@mit.edu, lists@peufeu.com, alvherre@commandprompt.com, dcrooke@gmail.com
Subject: Re: Block at a time ...
In-Reply-To: <27894.1268836024@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