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

Re: pg_largeobject and toast

From: yamt(at)mwd(dot)biglobe(dot)ne(dot)jp (YAMAMOTO Takashi)
To: tgl(at)sss(dot)pgh(dot)pa(dot)us
Cc: pgsql-novice(at)postgresql(dot)org
Subject: Re: pg_largeobject and toast
Date: 2010-12-22 05:33:28
Message-ID: 20101222053328.B94FE19D550@mail.netbsd.org (view raw or flat)
Thread:
Lists: pgsql-novice
hi,

> yamt(at)mwd(dot)biglobe(dot)ne(dot)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

In response to

Responses

pgsql-novice by date

Next:From: Tom LaneDate: 2010-12-22 15:12:31
Subject: Re: pg_largeobject and toast
Previous:From: Lukasz BrodziakDate: 2010-12-21 12:22:49
Subject: Re: Problem with select statement for duplicate data

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