Re: [HACKERS] pg_fallocate

2013-11-07 Thread Oskari Saarenmaa
On Thu, Oct 31, 2013 at 01:16:44PM +, Mitsumasa KONDO wrote: > --- a/src/backend/storage/file/fd.c > +++ b/src/backend/storage/file/fd.c > @@ -383,6 +383,21 @@ pg_flush_data(int fd, off_t offset, off_t amount) > return 0; > } > > +/* > + * pg_fallocate --- advise OS that the data pre-a

Re: [HACKERS] pg_fallocate

2013-11-06 Thread Peter Eisentraut
On 10/31/13, 9:16 AM, Mitsumasa KONDO wrote: > I'l like to add fallocate() system call to improve sequential read/write > peformance. fallocate() system call is different from posix_fallocate() > that is zero-fille algorithm to reserve continues disk space. > fallocate() is almost less overhead alo

Re: [HACKERS] pg_fallocate

2013-10-31 Thread Robert Haas
On Thu, Oct 31, 2013 at 9:16 AM, Mitsumasa KONDO wrote: > I'l like to add fallocate() system call to improve sequential read/write > peformance. fallocate() system call is different from posix_fallocate() that > is zero-fille algorithm to reserve continues disk space. fallocate() is > almost less

[HACKERS] pg_fallocate

2013-10-31 Thread Mitsumasa KONDO
Hi, I'l like to add fallocate() system call to improve sequential read/write peformance. fallocate() system call is different from posix_fallocate() that is zero-fille algorithm to reserve continues disk space. fallocate() is almost less overhead alogotithm to reserve continues disk space than pos