Mike <[EMAIL PROTECTED]> 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
---------------------------(end of broadcast)---------------------------
TIP 9: In versions below 8.0, the planner will ignore your desire to
choose an index scan if your joining column's datatypes do not
match
