| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Simon Riggs <simon(at)2ndquadrant(dot)com> |
| Cc: | ITAGAKI Takahiro <itagaki(dot)takahiro(at)oss(dot)ntt(dot)co(dot)jp>, Alvaro Herrera <alvherre(at)commandprompt(dot)com>, pgsql-patches(at)postgresql(dot)org |
| Subject: | Re: table/index fillfactor control, try 2 |
| Date: | 2006-06-19 15:51:50 |
| Message-ID: | 19418.1150732310@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers pgsql-patches |
Simon Riggs <simon(at)2ndquadrant(dot)com> writes:
> This was a response to Itagaki's comment that there may be a class of
> parameter that changes more frequently than that. I can see that we
> might want that, so just trying to plan ahead to
> dynamically/automatically set parameters - I thought you'd be in favour
> of that rather than lots of hand-tuned static parameters for indexes.
Anything that's automatically set can be completely hidden within the
index AM, no?
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Florian Weimer | 2006-06-19 16:47:00 | Re: sync_file_range() |
| Previous Message | Simon Riggs | 2006-06-19 15:42:36 | Re: table/index fillfactor control, try 2 |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Joachim Wieland | 2006-06-19 23:18:10 | doc & regress for full time zone names |
| Previous Message | Simon Riggs | 2006-06-19 15:42:36 | Re: table/index fillfactor control, try 2 |