Postgresql capabilities question

Поиск
Список
Период
Сортировка
От John Wells
Тема Postgresql capabilities question
Дата
Msg-id 34044.172.16.2.4.1049330026.squirrel@192.168.2.4
обсуждение исходный текст
Ответы Re: Postgresql capabilities question  (Steve Atkins <steve@blighty.com>)
Re: Postgresql capabilities question  (Ryan Mahoney <ryan@paymentalliance.net>)
Re: Postgresql capabilities question  (Lincoln Yeoh <lyeoh@pop.jaring.my>)
Re: Postgresql capabilities question  ("scott.marlowe" <scott.marlowe@ihs.com>)
Список pgsql-general
I have a M$ Sql Server db that I'm porting to postgresql.  Approx. 24
tables from this old db can be combined in the new database into one
table, and it would be a bit more elegant to do this.

However, the combined table would be around 95000 rows in size.

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.

Thanks very much for your input.

John


В списке pgsql-general по дате отправления:

Предыдущее
От: Alvaro Herrera
Дата:
Сообщение: Re: Backend often crashing
Следующее
От: Steve Atkins
Дата:
Сообщение: Re: Postgresql capabilities question