Re: Are there performance advantages in storing bulky field in separate table?
| От | Robert Treat |
|---|---|
| Тема | Re: Are there performance advantages in storing bulky field in separate table? |
| Дата | |
| Msg-id | 200904081513.28242.xzilla@users.sourceforge.net обсуждение исходный текст |
| Ответ на | Re: Are there performance advantages in storing bulky field in separate table? (Ian Mayo <ianmayo@tesco.net>) |
| Ответы |
Re: Are there performance advantages in storing bulky field
in separate table?
|
| Список | 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 по дате отправления: