Re: Re: [COMMITTERS] pgsql: Update autovacuum to use reloptions instead of a system catalog,
От | Alvaro Herrera |
---|---|
Тема | Re: Re: [COMMITTERS] pgsql: Update autovacuum to use reloptions instead of a system catalog, |
Дата | |
Msg-id | 20090211194311.GP8924@alvh.no-ip.org обсуждение исходный текст |
Ответ на | Re: Re: [COMMITTERS] pgsql: Update autovacuum to use reloptions instead of a system catalog, (Tom Lane <tgl@sss.pgh.pa.us>) |
Ответы |
Re: Re: [COMMITTERS] pgsql: Update autovacuum to use reloptions
instead of a system catalog,
Re: Re: [COMMITTERS] pgsql: Update autovacuum to use reloptions instead of a system catalog, |
Список | pgsql-hackers |
Tom Lane wrote: > Alvaro Herrera <alvherre@commandprompt.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. The problem is where do we store the options?
В списке pgsql-hackers по дате отправления: