Zdenek Kotala <[email protected]> writes:
> Another potential problem with toast setting is that reloption is toastable
> and
> it could generates loops in detoasting pg_class tuples. For example toast
> chunk
> size cannot be implement like reloption (or pg_class should use every time
> default values).
Nonsense. Toast chunk size isn't going to become variable *at all*,
unless we go over to the proposed toast indexing method that allows
the chunks to be self-identifying; in which case there's no problem
in pg_class or anyplace else.
regards, tom lane
--
Sent via pgsql-hackers mailing list ([email protected])
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
