| From: | Greg Smith <gsmith(at)gregsmith(dot)com> |
|---|---|
| To: | Gregory Stark <stark(at)enterprisedb(dot)com> |
| Cc: | Robert Haas <robertmhaas(at)gmail(dot)com>, Postgres <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Updated posix fadvise patch v19 |
| Date: | 2008-11-15 07:45:28 |
| Message-ID: | Pine.GSO.4.64.0811150242530.7668@westnet.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Fri, 14 Nov 2008, Gregory Stark wrote:
> In particular I was hoping Zoltan who original reported the sequential
> file strategy stuff being helpful might be able to see if this works for
> him.
The original message there suggested it was particularly valuable when
working with a somewhat broken kernel that was handling multiple
simultaenous reads badly. I think the idea here is that if you've got an
OS that handles that situation well, then the fadvise calls don't help
much. But having them in there does improve the odds that the kernel will
do the right thing with the sequential reads.
--
* Greg Smith gsmith(at)gregsmith(dot)com http://www.gregsmith.com Baltimore, MD
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Greg Smith | 2008-11-15 08:53:55 | Re: Enabling archive_mode without restart |
| Previous Message | Gregory Stark | 2008-11-15 05:56:23 | Re: "ORDER BY" clause prevents "UPDATE WHERE CURRENT OF" |