From: | Itagaki Takahiro <itagaki(dot)takahiro(at)gmail(dot)com> |
---|---|
To: | Jesper Krogh <jesper(at)krogh(dot)cc> |
Cc: | pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: Make tuples_per_page pr. table configureable. |
Date: | 2010-09-22 02:33:47 |
Message-ID: | AANLkTim+c-g7tjXwq1_84ydqEer3JkmhqzTCrkozbXnV@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Wed, Sep 22, 2010 at 3:44 AM, Jesper Krogh <jesper(at)krogh(dot)cc> wrote:
> Command to set "tuples_per_page" is:
> ALTER TABLE <tablename> set (tuples_per_page = X)
> where 1 <= X <= 32.
The tuples_per_page means *minimal* number of tuples in a page, right?
A page may contain more tuples when the size of tuples are small enough.
If so, I think the parameter name is confusable because it sounds
*restrict* the number of tuples per page like fillfactor.
"min_tuples_per_page" might be better for the name.
I didn't read previous discussions, but did we have consensus that "number
of tuples" is better than other units for the parameter? For example,
"threshold bytes" or "percentage in a page" also seems to be reasonable for me.
--
Itagaki Takahiro
From | Date | Subject | |
---|---|---|---|
Next Message | Fujii Masao | 2010-09-22 02:50:03 | Re: Shutting down server from a backend process, e.g. walrceiver |
Previous Message | Abhijit Menon-Sen | 2010-09-22 02:32:57 | Re: repository size differences |