| From: | Douglas McNaught <doug(at)mcnaught(dot)org> |
|---|---|
| To: | Mike <akiany(at)gmail(dot)com> |
| Cc: | pgsql-general(at)postgresql(dot)org |
| Subject: | Re: Performance Question - Table Row Size |
| Date: | 2007-07-13 01:58:47 |
| Message-ID: | 87hco9njxk.fsf@suzuka.mcnaught.org |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
Mike <akiany(at)gmail(dot)com> writes:
> I see. Thank you for the elaborate response. I have a clearer idea of
> what is going on now. In designing my application I was thinking of
> storing pieces of my data as serialized python data structures into a
> binary field (no more than 15KB), while a friend was arguing I should
> store the data in other tables and relate the tables together. He was
> arguing storing binary data on a table, even though, it is not queried
> slows down other queries and with this.
A 15KB column value is going to be stored out-of-line in the TOAST
table anyway, so your table tuple will just contain a pointer to it,
which isn't very big. If you don't use that column value in a given
query its effect will be minimal.
-Doug
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Robert Treat | 2007-07-13 02:11:11 | Re: Force SSL / username combination |
| Previous Message | Stephen Frost | 2007-07-13 01:51:06 | Re: How to pg_dumpall without root password |