Re: Are there performance advantages in storing bulky field in separate table? - Mailing list pgsql-general

From Ian Mayo
Subject Re: Are there performance advantages in storing bulky field in separate table?
Date
Msg-id a0a470f10904080856y2fc387f1qf3120741db894647@mail.gmail.com
Whole thread Raw
In response to Re: Are there performance advantages in storing bulky field in separate table?  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: Are there performance advantages in storing bulky field in separate table?
Re: Are there performance advantages in storing bulky field in separate table?
List pgsql-general
Cheers Tom,

On Wed, Apr 8, 2009 at 4:47 PM, Tom Lane <tgl@sss.pgh.pa.us> wrote:
> Ian Mayo <ianmayo@tesco.net> writes:
>> [snip]
> No.  You'd basically be manually reinventing the TOAST mechanism;
> or the large object mechanism, if you choose to store the blob
> as a large object rather than a plain bytea field.  Either way,
> it won't physically be in the same table as the main row data.

fine, that keeps the design simpler

> If you're curious, this goes into some of the gory details:
> http://www.postgresql.org/docs/8.3/static/storage-toast.html

Oooh, no, much too gory for me.

>                        regards, tom lane

thanks again.

One more thing:  hey, did you hear?  I just got some advice from Tom Lane!

Ian

pgsql-general by date:

Previous
From: Greg Smith
Date:
Subject: Re: Now I am back, next thing. Final PGS tuning.
Next
From: "Kevin Grittner"
Date:
Subject: Re: SOLVED: tsearch2 dictionary for statute cites