Re: pg_largeobject and toast - Mailing list pgsql-novice

From Tom Lane
Subject Re: pg_largeobject and toast
Date
Msg-id 5083.1293030751@sss.pgh.pa.us
Whole thread Raw
In response to Re: pg_largeobject and toast  (yamt@mwd.biglobe.ne.jp (YAMAMOTO Takashi))
Responses Re: pg_largeobject and toast  (yamt@mwd.biglobe.ne.jp (YAMAMOTO Takashi))
List pgsql-novice
yamt@mwd.biglobe.ne.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

pgsql-novice by date:

Previous
From: yamt@mwd.biglobe.ne.jp (YAMAMOTO Takashi)
Date:
Subject: Re: pg_largeobject and toast
Next
From: Mladen Gogala
Date:
Subject: Does Skype outage have anything to do with PostgreSQL?