[GENERAL] Are there performance advantages in storing bulky field in separate table?

2009-04-08 Thread Ian Mayo
Hi all, I'm designing a Postgresql database, and would appreciate this design advice. I've got a fairly straightforward table that's similar to a blog table (entryId, date, title, author, etc). There is, however, the requirement to allow a single, fairly bulky binary attachment to around 1% of th

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

2009-04-08 Thread Ian Mayo
Cheers Tom, On Wed, Apr 8, 2009 at 4:47 PM, Tom Lane wrote: > Ian Mayo 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 f

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

2009-04-08 Thread Ian Mayo
On Wed, Apr 8, 2009 at 8:13 PM, Robert Treat wrote: > 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. thanks for that Robert - it does match my (completely groundless) first im