|From:||John Lumby <johnlumby(at)hotmail(dot)com>|
|To:||Heikki Linnakangas <hlinnakangas(at)vmware(dot)com>, Claudio Freire <klaussfreire(at)gmail(dot)com>, pgsql hackers <pgsql-hackers(at)postgresql(dot)org>|
|Cc:||Greg Stark <stark(at)mit(dot)edu>, "andres(at)2ndquadrant(dot)com" <andres(at)2ndquadrant(dot)com>|
|Subject:||Re: Extended Prefetching using Asynchronous IO - proposal and patch|
|Views:||Raw Message | Whole Thread | Download mbox | Resend email|
I am attaching a new version of the patch for consideration in the current commit fest.
Relative to the one I submitted on 25 June in BAY175-W412FF89303686022A9F16AA3190(at)phx(dot)gbl
the method for handling aio completion using sigevent has been re-written to use
signals exclusively rather than a composite of signals and LWlocks,
and this has fixed the problem I mentioned before with the LWlock method.
More details are in postgresql-prefetching-asyncio.README
"Checking AIO Completion"
I also have worked my benchmark database and one application into a publishable state.
However, the database is in the form of a compressed pg_dump and is around
218 MB in size. I was hoping to come up with a generation program to load it
but have not had the time for that. Is there some place on postgresql.org for
such a large file? If not I will try to think of some place for it.
|Next Message||Alvaro Herrera||2014-08-19 21:42:06||Re: [patch] pg_copy - a command for reliable WAL archiving|
|Previous Message||Andres Freund||2014-08-19 20:27:34||Re: 9.3: more problems with "Could not open file "pg_multixact/members/xxxx"|
|Next Message||Adrian Klaver||2014-08-19 21:53:53||Re: ERROR: Problem running post install step|
|Previous Message||Larry White||2014-08-19 20:34:56||Anyone using Apache Helix to manage a PostgreSQL cluster?|