| From: | Magnus Hagander <magnus(at)hagander(dot)net> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Heikki Linnakangas <heikki(dot)linnakangas(at)enterprisedb(dot)com>, Dave Page <dpage(at)pgadmin(dot)org>, Josh Berkus <josh(at)agliodbs(dot)com>, Robert Haas <robertmhaas(at)gmail(dot)com>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: Closing some 8.4 open items |
| Date: | 2009-04-08 18:21:30 |
| Message-ID: | 49DCEB2A.6050901@hagander.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Tom Lane wrote:
> Magnus Hagander <magnus(at)hagander(dot)net> writes:
>> Heikki Linnakangas wrote:
>>> cygwin supports POSIX_FADV_SEQUENTIAL (and POSIX_FADV_NORMAL to revert
>>> it), but not any of the other flags. It maps it to
>>> NtSetInformationFile() like this:
>
>> We set this in our open() wrapper in the code today.
>
> Really? Where? I didn't find any of the mentioned symbols in a quick
> grep.
We pass FILE_FLAG_SEQUENTIAL_SCAN to the open call if O_SEQUENTIAL is
specified.
> I'm not sure how Windows interprets FILE_SEQUENTIAL_ONLY, but if that
> really means that it assumes *only* sequential accesses will happen,
> I'm not sure that we'd want to turn it on.
It's an access-optimization hint, that's all.
//Magnus
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Dave Page | 2009-04-08 18:25:20 | Re: Closing some 8.4 open items |
| Previous Message | Tom Lane | 2009-04-08 18:16:36 | Re: Closing some 8.4 open items |