From: | "Qingqing Zhou" <zhouqq(at)cs(dot)toronto(dot)edu> |
---|---|
To: | pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: what is the smallest working page size for postgresql |
Date: | 2005-12-23 02:01:09 |
Message-ID: | dofln6$no6$1@news.hub.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
"Hannu Krosing" <hannu(at)skype(dot)net> wrote
>
> Could anybody tell me what is the smallest working page size for
> postgresql ?
>
> I have a table where access is highly random over huge table getting
> usually only one small tuple from each page. One way to get more
> performance could be using smaller page size, so the per-tuple read
> overhead would be smaller.
>
> Would 4k pages work ? what about 2k and 1k ? 512bytes ?
>
> What would it take, to make only heap pages small and keep index pages
> larger ? Probably at least per-tablespace or per-pagesize split shared
> buffer space and changes in caching algorithms ?
>
I recall there was a discussion several weeks ago:
http://archives.postgresql.org/pgsql-performance/2005-12/msg00120.php
I bet block size less than 512 won't bring you any benefits, since that's
the physical disk sector size limit.
Regards,
Qingqing
From | Date | Subject | |
---|---|---|---|
Next Message | Bruce Momjian | 2005-12-23 02:04:40 | Re: Disparity in search_path SHOW and SET |
Previous Message | Tom Lane | 2005-12-23 01:21:54 | Re: [pgadmin-hackers] Client-side password encryption |