Re: pg_largeobject and toast - Mailing list pgsql-novice

From yamt@mwd.biglobe.ne.jp (YAMAMOTO Takashi)
Subject Re: pg_largeobject and toast
Date
Msg-id 20101222053328.B94FE19D550@mail.netbsd.org
Whole thread Raw
In response to Re: pg_largeobject and toast  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: pg_largeobject and toast
List pgsql-novice
hi,

> yamt@mwd.biglobe.ne.jp (YAMAMOTO Takashi) writes:
>> what's a supposed way for a user to create a toast table?
>> the comment in include/storage/large_object.h
>> ("unless the user creates a toast-table for pg_largeobject...")
>> made me think there's a way, but i couldn't find one.
>
> 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.  It's not recommended of course; given the usage of the table,
> it could only be a performance loss.

thanks for explanation.

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?

YAMAMOTO Takashi

>
>             regards, tom lane

pgsql-novice by date:

Previous
From: Lukasz Brodziak
Date:
Subject: Re: Problem with select statement for duplicate data
Next
From: Tom Lane
Date:
Subject: Re: pg_largeobject and toast