| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Alvaro Herrera <alvherre(at)commandprompt(dot)com> |
| Cc: | pgsql-performance(at)postgresql(dot)org, Pg Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: [HACKERS] autovacuum: use case for indenpedent TOAST table autovac settings |
| Date: | 2008-08-14 01:30:26 |
| Message-ID: | 21063.1218677426@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers pgsql-performance |
Alvaro Herrera <alvherre(at)commandprompt(dot)com> writes:
> Tom Lane wrote:
>> It seems like we'll want to do it somehow. Perhaps the cleanest way is
>> to incorporate toast-table settings in the reloptions of the parent
>> table. Otherwise dump/reload is gonna be a mess.
> My question is whether there is interest in actually having support for
> this, or should we just inherit the settings from the main table. My
> gut feeling is that this may be needed in some cases, but perhaps I'm
> overengineering the thing.
It seems reasonable to inherit the parent's settings by default, in any
case. So you could do that now and then extend the feature later if
there's real demand.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Decibel! | 2008-08-14 01:31:19 | Re: SeqScan costs |
| Previous Message | Alvaro Herrera | 2008-08-14 01:28:34 | Re: [HACKERS] autovacuum: use case for indenpedent TOAST table autovac settings |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Craig Ringer | 2008-08-14 01:48:03 | Re: Incorrect estimates on correlated filters |
| Previous Message | Alvaro Herrera | 2008-08-14 01:28:34 | Re: [HACKERS] autovacuum: use case for indenpedent TOAST table autovac settings |