Re: Closing some 8.4 open items

From: "Jignesh K(dot) Shah" <J(dot)K(dot)Shah(at)Sun(dot)COM>
To: Josh Berkus <josh(at)agliodbs(dot)com>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Robert Haas <robertmhaas(at)gmail(dot)com>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: Closing some 8.4 open items
Date: 2009-04-09 18:26:03
Message-ID: 49DE3DBB.7010905@sun.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 04/08/09 13:10, Josh Berkus wrote:
> On 4/8/09 9:44 AM, Tom Lane wrote:
>> Josh Berkus<josh(at)agliodbs(dot)com> writes:
>>> What about seq scans?
>>
>> If the kernel can't read-ahead a seqscan by itself, it's unlikely to
>> be smart enough to be helped by posix_fadvise ... or at least so I
>> would think. Do you have reason to think differently?
>
> Well, Solaris 10 + UFS should be helped by fadvise -- in theory at
> least, it would eliminate the need to modify your mount points for
> better readahead when setting up a PG-Solaris server. Solaris-UFS
> quite lazy about readahead. Zdenek, Jignesh?
>
Definitely this helps.. specially since forcedirectio hurts CLOGs and
helps WAL .. something that can be done without really impacting the
whole file system always helps.

Solaris by default only does readahead upto 56K and max tunable is 1MB.
If you use forcedirectio there is no readahead by the filesystem itself

ZFS is different it has no forcedirectio and hence fadvise flag for now
is ignored.

Regards,
Jignesh

> You're probably correct about Linux and FreeBSD. I don't know if OSX
> + HFS supports fadvise. If so, it could only help; readahead on HFS
> right now is nonexistant.
>
> Presumably fadvise is useless on Windows. Anyone know?
>
>

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Kevin Grittner 2009-04-09 18:30:21 Re: Re: [BUGS] BUG #4027: backslash escaping notdisabled inplpgsql
Previous Message Josh Berkus 2009-04-09 18:24:28 Re: Closing some 8.4 open items