| From: | Simon Riggs <simon(at)2ndquadrant(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| 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:42:36 |
| Message-ID: | 1150731756.2691.1159.camel@localhost.localdomain |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers pgsql-patches |
On Mon, 2006-06-19 at 09:15 -0400, Tom Lane wrote:
> Simon Riggs <simon(at)2ndquadrant(dot)com> writes:
> > Looks like we've got a class of data that is similar in its frequency of
> > change to the pg_class_nt stuff.
>
> Say what? These parameters wouldn't ever change after creation, unless
> we invent ALTER commands to change them.
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.
--
Simon Riggs
EnterpriseDB http://www.enterprisedb.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2006-06-19 15:51:50 | Re: table/index fillfactor control, try 2 |
| Previous Message | Tom Lane | 2006-06-19 15:17:48 | Getting rid of extra gettimeofday() calls |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2006-06-19 15:51:50 | Re: table/index fillfactor control, try 2 |
| Previous Message | Tom Lane | 2006-06-19 13:15:59 | Re: table/index fillfactor control, try 2 |