Zdenek Kotala <Zdenek(dot)Kotala(at)Sun(dot)COM> 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
In response to
pgsql-hackers by date
|Next:||From: Tom Lane||Date: 2008-12-21 17:43:29|
|Subject: Re: Is "Window" really safe as a global typedef name? |
|Previous:||From: Andreas 'ads' Scherbaum||Date: 2008-12-21 13:05:16|
|Subject: [patch] Reformat permissions in \l+ (like \z does)|