Re: Re: [COMMITTERS] pgsql: Update autovacuum to use reloptions instead of a system catalog,

From: Alvaro Herrera <alvherre(at)commandprompt(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: ITAGAKI Takahiro <itagaki(dot)takahiro(at)oss(dot)ntt(dot)co(dot)jp>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: Re: [COMMITTERS] pgsql: Update autovacuum to use reloptions instead of a system catalog,
Date: 2009-02-11 20:48:17
Message-ID: 20090211204817.GW8924@alvh.no-ip.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-committers pgsql-hackers

Tom Lane wrote:

> Or to put it another way: it seems to me that the use-case being argued
> here is really for being able to adjust the default toast reloptions.
> Not to have action at a distance on a table that doesn't exist and you
> have no way to know when you set the option what will be in it when it
> does exist.

This argument makes perfect sense to me.

Since we don't have a way to set default reloptions for main tables
either, I don't think we should be pushing very hard for having one to
set default reloptions for toast tables.

Even if we were to argue that we should have both, it doesn't seem
material for 8.4.

In response to

Responses

Browse pgsql-committers by date

  From Date Subject
Next Message Tom Lane 2009-02-11 21:11:16 pgsql: Change ALTER TABLE SET WITHOUT OIDS to rewrite the whole table to
Previous Message Tom Lane 2009-02-11 20:40:33 Re: Re: [COMMITTERS] pgsql: Update autovacuum to use reloptions instead of a system catalog,

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2009-02-11 21:21:38 Re: Re: [COMMITTERS] pgsql: Update autovacuum to use reloptions instead of a system catalog,
Previous Message Tom Lane 2009-02-11 20:40:33 Re: Re: [COMMITTERS] pgsql: Update autovacuum to use reloptions instead of a system catalog,