Re: pg_largeobject and toast

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: yamt(at)mwd(dot)biglobe(dot)ne(dot)jp (YAMAMOTO Takashi)
Cc: pgsql-novice(at)postgresql(dot)org
Subject: Re: pg_largeobject and toast
Date: 2010-12-22 15:12:31
Message-ID: 5083.1293030751@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-novice

yamt(at)mwd(dot)biglobe(dot)ne(dot)jp (YAMAMOTO Takashi) writes:
>> At one time there was an actual command ALTER TABLE foo CREATE TOAST TABLE
>> (or something close to that, don't recall the exact spelling) that
>> in principle could have been invoked on pg_largeobject. That's not
>> there anymore, but as you say it's still possible for pg_largeobject
>> to acquire a toast table if you're willing to perform random ALTERs
>> on it.

> is it too complicated to make the database bootstrap process perform
> SET STORAGE equivalent so that random ALTERs on the table doesn't
> trigger toast creation?

I guess the answer to that is what the heck are you doing doing random
ALTERs on a system catalog? It's not clear to me that we should be
putting in kluges to cause such things to have nonstandard effects.
Superusers are assumed to know what they're doing.

regards, tom lane

In response to

Responses

Browse pgsql-novice by date

  From Date Subject
Next Message Ramroth, Laurie 2010-12-22 22:57:14 SQL state 42601 FOR syntax error
Previous Message YAMAMOTO Takashi 2010-12-22 05:33:28 Re: pg_largeobject and toast