I have added this to TODO.detail/mmap.
> I have just completed the functional testing the WAL using mmap , it is
>
> working fine, I have tested by commenting out the "CreateCheckPoint "
> functionality so that
>when i kill the postgres and restart it will redo all the records
Sounds good. Keep us posted. This will probably not make it into 7.2
but can be added to 7.3. We can perhaps conditionally use your code in
place of what is there. I have also looked at reducing the write() size
for WAL secondary writes. That will have to wait for 7.3 too because we
are so n
I have just completed the functional testing the WAL using mmap , it is
working fine, I have tested by commenting out the "CreateCheckPoint "
functionality so that
when i kill the postgres and restart it will redo all the records from the
WAL log file which
is updated using m
> > Hi all,
> > By mapping the WAL files by each backend in to its address
> > space using "mmap" system call , there will be big
> > improvements in performance from the following point of view:
> > 1. Each backend directly writes in to the address
> > space
Janardhana Reddy <[EMAIL PROTECTED]> writes:
> By mapping the WAL files by each backend in to its address
> space using "mmap" system call ,
There are a lot of problems with trying to use mmap for Postgres. One
is portability: not all platforms have mmap, so we'd still have to
su
> Hi all,
> By mapping the WAL files by each backend in to its address
> space using "mmap" system call , there will be big
> improvements in performance from the following point of view:
> 1. Each backend directly writes in to the address
> space which is o
