| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> |
| Cc: | ITAGAKI Takahiro <itagaki(dot)takahiro(at)lab(dot)ntt(dot)co(dot)jp>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: TODO-Item: B-tree fillfactor control |
| Date: | 2006-02-01 18:22:17 |
| Message-ID: | 3185.1138818137@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers pgsql-patches |
Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> writes:
>> - Should indexes remember their fillfactors when they are created?
>> The last fillfactors will be used on next reindex.
> They should remember, for sure, and REINDEX should use it. It think
> this is similar to the ALTER TABLE ALTER [ COLUMN ] ... SET STATISTICS
> functionality. It will need to be dumped as well by pg_dump.
If you want it to be dumped by pg_dump (which is debatable IMHO) then
it MUST NOT be a syntax extension, it has to be driven by a GUC
variable, else we have compatibility problems with the dumps. We just
went through this with WITH/WITHOUT OIDS.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bruce Momjian | 2006-02-01 18:32:24 | Re: TODO-Item: B-tree fillfactor control |
| Previous Message | Tom Lane | 2006-02-01 18:18:31 | Re: [HACKERS] autovacuum |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bruce Momjian | 2006-02-01 18:30:43 | Re: New pg_dump options: exclude tables/schemas, multiple |
| Previous Message | Bruce Momjian | 2006-02-01 17:45:11 | Re: TODO-Item: B-tree fillfactor control |