Re: Are there performance advantages in storing bulky field in separate table?

From: Ian Mayo <ianmayo(at)tesco(dot)net>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: pgsql-general(at)postgresql(dot)org
Subject: Re: Are there performance advantages in storing bulky field in separate table?
Date: 2009-04-08 15:56:35
Message-ID: a0a470f10904080856y2fc387f1qf3120741db894647@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

Cheers Tom,

On Wed, Apr 8, 2009 at 4:47 PM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> Ian Mayo <ianmayo(at)tesco(dot)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

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Kevin Grittner 2009-04-08 16:04:57 Re: SOLVED: tsearch2 dictionary for statute cites
Previous Message Greg Smith 2009-04-08 15:52:38 Re: Now I am back, next thing. Final PGS tuning.