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

From: Alvaro Herrera <alvherre(at)commandprompt(dot)com>
To: ITAGAKI Takahiro <itagaki(dot)takahiro(at)oss(dot)ntt(dot)co(dot)jp>
Cc: 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 19:30:31
Message-ID: 20090211193031.GM8924@alvh.no-ip.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-committers pgsql-hackers

Alvaro Herrera wrote:
> ITAGAKI Takahiro wrote:
>
> > I tested this changes and found two issues:
> >
> > 1. fillfactor.* options are silently ignored when the table doesn't have
> > toast relation. Should we notice the behabior to users?
> > ex. NOTICE: toast storage parameters are ignored
> > because the table doesn't have toast relations.
>
> You mean "toast.* options"? If so, yes, they are silently ignored.
> Maybe issuing a warning is not a bad idea. Care to propose a patch?

Any takers here?

The second issue has been solved.

Thanks for testing.

In response to

Responses

Browse pgsql-committers by date

  From Date Subject
Next Message Tom Lane 2009-02-11 19:36:16 Re: Re: [COMMITTERS] pgsql: Update autovacuum to use reloptions instead of a system catalog,
Previous Message Alvaro Herrera 2009-02-11 19:12:43 Re: Re: [COMMITTERS] pgsql: Update autovacuum to use reloptions instead of a system catalog,

Browse pgsql-hackers by date

  From Date Subject
Next Message Bernd Helmle 2009-02-11 19:30:41 Re: HotStandby vs. flatfile updates
Previous Message Simon Riggs 2009-02-11 19:27:51 Re: HotStandby vs. flatfile updates