Josh Berkus <[EMAIL PROTECTED]> writes:
> Suggestion 3: There was an issue in 7.3 with table rows which are overly broad
> -- some problems with PSQL, I believe.
Not sure about PSQL, but I think there still are some performance issues
in the backend with SELECTs involving more than a couple hundr
Alexander,
> I am in the process of creating a database design in which LOTS of data
> need to be modelled.
>
> For instance, I need to store data about products. Every product has LOTS
> of properties, well over a hundred.
> Do any of you know if and how PostgreSQL would prefer one approach over
Hi guys,
I am in the process of creating a database design in which LOTS of data need
to be modelled.
For instance, I need to store data about products. Every product has LOTS of
properties, well over a hundred.
So I'm wondering. What's the best approach here, performance wise? Just
create one P
