Skip site navigation (1) Skip section navigation (2)

Re: reloptions and toast tables

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: (view raw, whole thread or download thread mbox)
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

In response to


pgsql-hackers by date

Next:From: Tom LaneDate: 2008-12-21 17:43:29
Subject: Re: Is "Window" really safe as a global typedef name?
Previous:From: Andreas 'ads' ScherbaumDate: 2008-12-21 13:05:16
Subject: [patch] Reformat permissions in \l+ (like \z does)

Privacy Policy | About PostgreSQL
Copyright © 1996-2017 The PostgreSQL Global Development Group