Re: reloptions and toast tables

From: Zdenek Kotala <Zdenek(dot)Kotala(at)Sun(dot)COM>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
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-22 07:43:32
Message-ID: 494F4524.6090503@sun.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Tom Lane napsal(a):
> 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.

I know. It was only example that some reloption cannot be applied on pg_class
relation and pg_class toast table, because it could introduce chicken/egg problem.

Zdenek

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message ITAGAKI Takahiro 2008-12-22 07:44:01 Re: contrib/pg_stat_statements 1212
Previous Message Alex Hunsaker 2008-12-22 05:37:50 Re: contrib/pg_stat_statements 1212