| From: | Kenneth Marshall <ktm(at)it(dot)is(dot)rice(dot)edu> |
|---|---|
| To: | Jim Nasby <jim(at)nasby(dot)net> |
| Cc: | Ron Mayer <rm_pg(at)cheapcomplexdevices(dot)com>, Gregory Stark <stark(at)enterprisedb(dot)com>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: [GENERAL] Autovacuum Improvements |
| Date: | 2007-01-24 13:40:31 |
| Message-ID: | 20070124134031.GD27859@it.is.rice.edu |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general pgsql-hackers |
On Tue, Jan 23, 2007 at 09:01:41PM -0600, Jim Nasby wrote:
> On Jan 22, 2007, at 6:53 PM, Kenneth Marshall wrote:
> >The default should
> >be approximately the OS standard read-ahead amount.
>
> Is there anything resembling a standard across the OSes we support?
> Better yet, is there a standard call that allows you to find out what
> the read-ahead setting is?
> --
> Jim Nasby jim(at)nasby(dot)net
> EnterpriseDB http://enterprisedb.com 512.569.9461 (cell)
>
Not that I am aware of. Even extending the relation by one additional
block can make a big difference in performance and should easily fall
within every read-ahead in use today. Or a GUC variable, that defaults
to a small power of 2 number of PostgreSQL blocks, with a default arrived
at by testing.
Ken
| From | Date | Subject | |
|---|---|---|---|
| Next Message | marcelo Cortez | 2007-01-24 14:08:02 | Re: how to read bytea field |
| Previous Message | Markus Schiltknecht | 2007-01-24 13:38:56 | Re: how to read bytea field |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Gregory Stark | 2007-01-24 14:08:51 | Re: Free space management within heap page |
| Previous Message | Zeugswetter Andreas ADI SD | 2007-01-24 13:27:53 | Re: Updateable cursors |