Re: Postgresql capabilities question

You're absolutely correct that there are *many* other factors that
determine performance aside from row count. That being said, I have
table with over a million entries on actively used systems that perform
really well with queries utilize and index and acceptably well on
queries that require a sequential scan.

> Having never really used Postgresql in the past, and unable to find a
> datapoint on the web, I would really like to get input from current users.
> Is this an unreasonable table size to expect good performance when the
> PHP app driving it gets a reasonable amount of traffic? I know
> performance is also heavily dependent on indexes and query structure, but
> disregarding either of those for the sake of argument, would I be better
> off keeping the tables separate, or is 95000 not something to worry about?
> btw, most tables in this database are quite small (<2000). My redesign
> would create two tables in the +90000 range, but less than 100000.