| From: | ITAGAKI Takahiro <itagaki(dot)takahiro(at)oss(dot)ntt(dot)co(dot)jp> |
|---|---|
| To: | pgsql-hackers(at)postgresql(dot)org |
| Subject: | fillfactor for toast tables is useless? |
| Date: | 2009-02-12 06:55:33 |
| Message-ID: | 20090212155219.87A0.52131E4D@oss.ntt.co.jp |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
With reloption patch, we can set WITH options to toast tables.
However, fillfactor for toast tables is useless, no?
(autovacuum options will work as expected, though.)
Tuples in toast tables are never updated. When the main tuple is updated,
old toast tuples are deleted and new ones are inserted. Even if there are
some freespaces in pages of toast table, they are never used by inserts.
I think we should not allow users to modify fillfactor for toast tables
and it should be always 100%.
We could optimize a delete+insert operation for toast tuples to one update
when the number of chunks are not changed by update.
Fillfactor for toast tables will be only useful after the optimization.
Regards,
---
ITAGAKI Takahiro
NTT Open Source Software Center
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tao Ma | 2009-02-12 07:35:52 | some questions about SELECT FOR UPDATE/SHARE |
| Previous Message | Peter Eisentraut | 2009-02-12 06:15:36 | Re: temporarily stop autovacuum |