pg.ddx.io pgsql-performance@postgresql.org mailing list archive
help / color / mirror / Atom feedautovacuum: use case for indenpedent TOAST table autovac settings
5+ messages / 3 participants
[nested] [flat]
* autovacuum: use case for indenpedent TOAST table autovac settings
@ 2008-08-13 21:28 Alvaro Herrera <alvherre@commandprompt.com>
2008-08-14 00:53 ` Re: autovacuum: use case for indenpedent TOAST table autovac settings Tom Lane <tgl@sss.pgh.pa.us>
0 siblings, 1 reply; 5+ messages in thread
From: Alvaro Herrera @ 2008-08-13 21:28 UTC (permalink / raw)
To: pgsql-performance@postgresql.org, Pg Hackers <pgsql-hackers@postgresql.org>
Hackers and PG users,
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.
--
Alvaro Herrera http://www.CommandPrompt.com/
The PostgreSQL Company - Command Prompt, Inc.
^ permalink raw reply [nested|flat] 5+ messages in thread
* Re: autovacuum: use case for indenpedent TOAST table autovac settings
2008-08-13 21:28 autovacuum: use case for indenpedent TOAST table autovac settings Alvaro Herrera <alvherre@commandprompt.com>
@ 2008-08-14 00:53 ` Tom Lane <tgl@sss.pgh.pa.us>
2008-08-14 01:28 ` Re: [HACKERS] autovacuum: use case for indenpedent TOAST table autovac settings Alvaro Herrera <alvherre@commandprompt.com>
0 siblings, 1 reply; 5+ messages in thread
From: Tom Lane @ 2008-08-14 00:53 UTC (permalink / raw)
To: Alvaro Herrera <alvherre@commandprompt.com>; +Cc: pgsql-performance@postgresql.org, Pg Hackers <pgsql-hackers@postgresql.org>
Alvaro Herrera <alvherre@commandprompt.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
^ permalink raw reply [nested|flat] 5+ messages in thread
* Re: [HACKERS] autovacuum: use case for indenpedent TOAST table autovac settings
2008-08-13 21:28 autovacuum: use case for indenpedent TOAST table autovac settings Alvaro Herrera <alvherre@commandprompt.com>
2008-08-14 00:53 ` Re: autovacuum: use case for indenpedent TOAST table autovac settings Tom Lane <tgl@sss.pgh.pa.us>
@ 2008-08-14 01:28 ` Alvaro Herrera <alvherre@commandprompt.com>
2008-08-14 01:30 ` Re: [HACKERS] autovacuum: use case for indenpedent TOAST table autovac settings Tom Lane <tgl@sss.pgh.pa.us>
0 siblings, 1 reply; 5+ messages in thread
From: Alvaro Herrera @ 2008-08-14 01:28 UTC (permalink / raw)
To: Tom Lane <tgl@sss.pgh.pa.us>; +Cc: pgsql-performance@postgresql.org, Pg Hackers <pgsql-hackers@postgresql.org>
Tom Lane wrote:
> Alvaro Herrera <alvherre@commandprompt.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.
Yeah, Magnus was suggesting this syntax:
ALTER TABLE foo SET toast_autovacuum_enable = false;
and the like.
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.
--
Alvaro Herrera http://www.CommandPrompt.com/
PostgreSQL Replication, Consulting, Custom Development, 24x7 support
^ permalink raw reply [nested|flat] 5+ messages in thread
* Re: [HACKERS] autovacuum: use case for indenpedent TOAST table autovac settings
2008-08-13 21:28 autovacuum: use case for indenpedent TOAST table autovac settings Alvaro Herrera <alvherre@commandprompt.com>
2008-08-14 00:53 ` Re: autovacuum: use case for indenpedent TOAST table autovac settings Tom Lane <tgl@sss.pgh.pa.us>
2008-08-14 01:28 ` Re: [HACKERS] autovacuum: use case for indenpedent TOAST table autovac settings Alvaro Herrera <alvherre@commandprompt.com>
@ 2008-08-14 01:30 ` Tom Lane <tgl@sss.pgh.pa.us>
2008-08-14 09:51 ` Re: [HACKERS] autovacuum: use case for indenpedent TOAST table autovac settings Simon Riggs <simon@2ndquadrant.com>
0 siblings, 1 reply; 5+ messages in thread
From: Tom Lane @ 2008-08-14 01:30 UTC (permalink / raw)
To: Alvaro Herrera <alvherre@commandprompt.com>; +Cc: pgsql-performance@postgresql.org, Pg Hackers <pgsql-hackers@postgresql.org>
Alvaro Herrera <alvherre@commandprompt.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
^ permalink raw reply [nested|flat] 5+ messages in thread
* Re: [HACKERS] autovacuum: use case for indenpedent TOAST table autovac settings
2008-08-13 21:28 autovacuum: use case for indenpedent TOAST table autovac settings Alvaro Herrera <alvherre@commandprompt.com>
2008-08-14 00:53 ` Re: autovacuum: use case for indenpedent TOAST table autovac settings Tom Lane <tgl@sss.pgh.pa.us>
2008-08-14 01:28 ` Re: [HACKERS] autovacuum: use case for indenpedent TOAST table autovac settings Alvaro Herrera <alvherre@commandprompt.com>
2008-08-14 01:30 ` Re: [HACKERS] autovacuum: use case for indenpedent TOAST table autovac settings Tom Lane <tgl@sss.pgh.pa.us>
@ 2008-08-14 09:51 ` Simon Riggs <simon@2ndquadrant.com>
0 siblings, 0 replies; 5+ messages in thread
From: Simon Riggs @ 2008-08-14 09:51 UTC (permalink / raw)
To: Tom Lane <tgl@sss.pgh.pa.us>; +Cc: Alvaro Herrera <alvherre@commandprompt.com>; pgsql-performance@postgresql.org, Pg Hackers <pgsql-hackers@postgresql.org>
On Wed, 2008-08-13 at 21:30 -0400, Tom Lane wrote:
> Alvaro Herrera <alvherre@commandprompt.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.
Yeh, I can't really see a reason why you'd want to treat toast tables
differently with regard to autovacuuming. It's one more setting to get
wrong, so no thanks.
--
Simon Riggs www.2ndQuadrant.com
PostgreSQL Training, Services and Support
^ permalink raw reply [nested|flat] 5+ messages in thread
end of thread, other threads:[~2008-08-14 09:51 UTC | newest]
Thread overview: 5+ messages (download: mbox mbox.gz follow: Atom feed)
-- links below jump to the message on this page --
2008-08-13 21:28 autovacuum: use case for indenpedent TOAST table autovac settings Alvaro Herrera <alvherre@commandprompt.com>
2008-08-14 00:53 ` Tom Lane <tgl@sss.pgh.pa.us>
2008-08-14 01:28 ` Alvaro Herrera <alvherre@commandprompt.com>
2008-08-14 01:30 ` Tom Lane <tgl@sss.pgh.pa.us>
2008-08-14 09:51 ` Simon Riggs <simon@2ndquadrant.com>
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox