From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Alvaro Herrera <alvherre(at)commandprompt(dot)com> |
Cc: | Peter Eisentraut <peter_e(at)gmx(dot)net>, pgsql-hackers(at)postgresql(dot)org, Euler Taveira de Oliveira <euler(at)timbira(dot)com> |
Subject: | Re: reloptions and toast tables |
Date: | 2008-12-31 21:45:57 |
Message-ID: | 15638.1230759957@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Alvaro Herrera <alvherre(at)commandprompt(dot)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
From | Date | Subject | |
---|---|---|---|
Next Message | Pavel Stehule | 2008-12-31 21:55:22 | Re: sum() over (partition by order) question |
Previous Message | Tom Lane | 2008-12-31 21:36:27 | Re: sum() over (partition by order) question |