| From: | Merlin Moncure <mmoncure(at)gmail(dot)com> |
|---|---|
| To: | Bartosz Dmytrak <bdmytrak(at)gmail(dot)com> |
| Cc: | "pgsql-general(at)postgresql(dot)org" <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: effective_io_concurrency on Windows |
| Date: | 2013-03-26 13:28:17 |
| Message-ID: | CAHyXU0yg7QjP1WxX_=MMQMZMMH8THtasqDgfAqMZvqn8gpMcRQ@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Tue, Mar 26, 2013 at 3:35 AM, Bartosz Dmytrak <bdmytrak(at)gmail(dot)com> wrote:
> Hi all
> is it possible to introduce similar solution for Windows systems in future?
> I am aware it is not available because of lack of posix_fadvise function,
> but I believe there is a way to introduce this feature for Win systems.
Probably the best case scenario would be to make some library routines
that wrap the windows API and emulate posix_fadvise. This may or may
not be possible, but win32 API does support asynchronous i/o so it
might be.
merlin
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Richard Huxton | 2013-03-26 14:00:26 | Re: Do "after update" trigger block the current transaction? |
| Previous Message | Clemens Eisserer | 2013-03-26 13:24:56 | Re: Do "after update" trigger block the current transaction? |