| 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: autovacuum: use case for indenpedent TOAST table autovac settings |
| Date: | 2008-08-14 00:53:10 |
| Message-ID: | 18539.1218675190@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:
> Does anyone see a need for having TOAST tables be individually
> configurable for autovacuum? I've finally come around to looking at
> being able to use ALTER TABLE for autovacuum settings, and I'm wondering
> if we need to support that case.
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.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Alvaro Herrera | 2008-08-14 01:28:34 | Re: [HACKERS] autovacuum: use case for indenpedent TOAST table autovac settings |
| Previous Message | Tom Lane | 2008-08-14 00:44:00 | Re: SeqScan costs |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Alvaro Herrera | 2008-08-14 01:28:34 | Re: [HACKERS] autovacuum: use case for indenpedent TOAST table autovac settings |
| Previous Message | Ron Mayer | 2008-08-13 22:30:40 | Re: Filesystem benchmarking for pg 8.3.3 server |