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

From Robert Treat
Subject Re: Are there performance advantages in storing bulky field in separate table?
Date
Msg-id 200904081513.28242.xzilla@users.sourceforge.net
Whole thread Raw
In response to Re: Are there performance advantages in storing bulky field in separate table?  (Ian Mayo <ianmayo@tesco.net>)
Responses Re: Are there performance advantages in storing bulky field in separate table?
List pgsql-general
On Wednesday 08 April 2009 11:56:35 Ian Mayo wrote:
> 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
>

Maybe I've been reading too much Pascal again lately, but if only 1% of your
rows are going to have data in this column, personally, I'd put it in a
separate table.

--
Robert Treat
Conjecture: http://www.xzilla.net
Consulting: http://www.omniti.com

pgsql-general by date:

Previous
From: Greg Smith
Date:
Subject: Re: Now I am back, next thing. Final PGS tuning.
Next
From: Steve Crawford
Date:
Subject: Re: Table has 22 million records, but backup doesn't see them