Re: reloptions and toast tables - Mailing list pgsql-hackers

From Tom Lane
Subject Re: reloptions and toast tables
Date
Msg-id 15638.1230759957@sss.pgh.pa.us
Whole thread Raw
In response to Re: reloptions and toast tables  (Alvaro Herrera <alvherre@commandprompt.com>)
Responses Re: reloptions and toast tables  ("Dave Page" <dpage@pgadmin.org>)
Re: reloptions and toast tables  (Alvaro Herrera <alvherre@commandprompt.com>)
List pgsql-hackers
Alvaro Herrera <alvherre@commandprompt.com> writes:
> Peter Eisentraut wrote:
>> On Sunday 21 December 2008 01:48:42 Alvaro Herrera wrote:
>>> ALTER TABLE foo SET (TOAST autovacuum_enabled = false);
>>> ALTER TABLE foo SET (toast.autovacuum_enabled = false);
>>> ALTER TABLE foo TOAST SET (autovacuum_enabled = false);
>>> ALTER TABLE foo SET TOAST (autovacuum_enabled = false);
>> 
>> The last two don't appear to allow setting TOAST and non-TOAST options in one 
>> go.  I think it would be handy to allow that, though.

> Agreed -- so I'm now playing with this version:

> ALTER TABLE foo SET (TOAST autovacuum_enabled = false);

> So the grammar modifications needed to accept that are attached.  The
> support code is a lot messier than I'd like :-(

This is not only really ugly, but 100% toast-specific.  The
qualified-name approach ("toast.autovacuum_enabled") has at least
a chance of being good for something else.  Or just make it
toast_autovacuum_enabled and do the translation magic at some low
level in the statement execution code.
        regards, tom lane


pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: sum() over (partition by order) question
Next
From: "Jaime Casanova"
Date:
Subject: Re: sum() over (partition by order) question