Tom Lane wrote: > Alvaro Herrera <alvhe...@commandprompt.com> writes: > > Tom Lane wrote: > >> 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? > > We don't. If there's no toast table, we don't need them after all.
Well, that's the position that the current code is taking. However, Takahiro-san and Euler's position is that if you do this: create table foo (f1 int) with (toast.fillfactor = 70); alter table foo add column f2 text; Then the toast table should have the fillfactor setting. Right now they are lost. If we agree that the options are OK to be lost, then there's nothing we need to do (and that's my opinion). If we don't, then we need some weird hack to make it work somehow. Personally I think that it needs a lot more work than it warrants. -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
