| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Alvaro Herrera <alvherre(at)commandprompt(dot)com> |
| 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 19:36:16 |
| Message-ID: | 13101.1234380976@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-committers pgsql-hackers |
Alvaro Herrera <alvherre(at)commandprompt(dot)com> writes:
> Alvaro Herrera wrote:
>> ITAGAKI Takahiro wrote:
>>> 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
>> 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?
I tend to think this isn't a very good idea. It's difficult for
applications to know whether a toast table will be created or not.
They should be able to just set the toast options and not worry.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Alvaro Herrera | 2009-02-11 19:43:11 | Re: Re: [COMMITTERS] pgsql: Update autovacuum to use reloptions instead of a system catalog, |
| Previous Message | Alvaro Herrera | 2009-02-11 19:30:31 | Re: Re: [COMMITTERS] pgsql: Update autovacuum to use reloptions instead of a system catalog, |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Alvaro Herrera | 2009-02-11 19:43:11 | Re: Re: [COMMITTERS] pgsql: Update autovacuum to use reloptions instead of a system catalog, |
| Previous Message | Bernd Helmle | 2009-02-11 19:30:41 | Re: HotStandby vs. flatfile updates |