Re: fallocate / posix_fallocate for new WAL file creation (etc...)

From: Stephen Frost <sfrost(at)snowman(dot)net>
To: Andres Freund <andres(at)2ndquadrant(dot)com>
Cc: Peter Eisentraut <peter_e(at)gmx(dot)net>, Robert Haas <robertmhaas(at)gmail(dot)com>, Greg Smith <greg(at)2ndquadrant(dot)com>, Jon Nelson <jnelson+pgsql(at)jamponi(dot)net>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: fallocate / posix_fallocate for new WAL file creation (etc...)
Date: 2013-05-30 12:53:37
Message-ID: 20130530125337.GR6434@tamriel.snowman.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

* Andres Freund (andres(at)2ndquadrant(dot)com) wrote:
> But really, I am not at all concerned about some obscure values being
> returned, but about a read() not being successful..

Alright, so what do we need to do to test this? We really just need a
short C program written up and then a bunch of folks to run it on
various architectures, right? Gee, sounds like what the buildfarm was
made for (alright, alright, PostgreSQL isn't exactly a 'short C
program', but you get the idea). As I recall, Andrew reworked the
buildfarm code to be more modular too.. Anyone have thoughts about how
we could run these kinds of tests with it? Or do people think that's a
bad idea?

Thanks,

Stephen

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Andres Freund 2013-05-30 12:58:26 Re: fallocate / posix_fallocate for new WAL file creation (etc...)
Previous Message Stephen Frost 2013-05-30 12:50:38 Re: fallocate / posix_fallocate for new WAL file creation (etc...)