From: | Seum-Lim Gan <slgan(at)lucent(dot)com> |
---|---|
To: | pgsql-performance(at)postgresql(dot)org |
Cc: | ahsaleh(at)lucent(dot)com |
Subject: | PostgreSQL Disk Usage and Page Size |
Date: | 2004-03-17 23:52:13 |
Message-ID: | p0510034bbc7e94bbd838@[135.185.171.143] |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-performance |
Hi all,
we have a question about the pagesize in PostgreSQL:
Using different pagesizes: 4K, 8K, 16K, 32K, when we store different
record sizes
such as in the following example:
CREATE TABLE TEST_1 (
F1 VARCHAR(10),
F2 VARCHAR(5) );
CREATE TABLE TEST_2 (
F1 VARCHAR(10),
F2 VARCHAR(10) );
we're consistently having the following storage behavior:
60 records / 4k_page
120 records / 8k_page
240 records / 16k_page
480 records / 32k_page.
So it seems that it doesn't matter whether the record size is
15 bytes or 20 bytes, there's maximum number of records per page
as shown above.
Any clues if there's any parameter or bug causing that?
Gan (for Amgad)
--
+--------------------------------------------------------+
| Seum-Lim GAN email : slgan(at)lucent(dot)com |
| Lucent Technologies |
| 2000 N. Naperville Road, 6B-403F tel : (630)-713-6665 |
| Naperville, IL 60566, USA. fax : (630)-713-7272 |
| web : http://inuweb.ih.lucent.com/~slgan |
+--------------------------------------------------------+
From | Date | Subject | |
---|---|---|---|
Next Message | Stephen Robert Norris | 2004-03-18 00:07:35 | Re: PostgreSQL Disk Usage and Page Size |
Previous Message | Matthew T. O'Connor | 2004-03-17 20:57:09 | Re: rapid degradation after postmaster restart |