From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Zdenek Kotala <Zdenek(dot)Kotala(at)Sun(dot)COM> |
Cc: | Alvaro Herrera <alvherre(at)commandprompt(dot)com>, Euler Taveira de Oliveira <euler(at)timbira(dot)com>, Pg Hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: reloptions and toast tables |
Date: | 2008-12-21 17:34:14 |
Message-ID: | 4525.1229880854@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
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
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2008-12-21 17:43:29 | Re: Is "Window" really safe as a global typedef name? |
Previous Message | Andreas 'ads' Scherbaum | 2008-12-21 13:05:16 | [patch] Reformat permissions in \l+ (like \z does) |