Search Postgresql Archives

Re: [Slony1-general] Using slony with many schema's

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 




On Oct 11, 2006, at 2:55 PM, snacktime wrote:

So by putting all the data into one schema, every report query now
gets run against a million or more rows instead of just a few  hundred
or thousand.  So all clients will see a drop in query performance
instead of just the clients with large amounts of data.

Indexes on the customer_id field of the combined data tables helps a lot. That and big hardware with big RAM. :-)

We store data for all our customers in the same tables. some have several hundred thousand of their own customers, and millions of transactions from them; others have a few hundred. The responsiveness of postgres is still great.

Attachment: smime.p7s
Description: S/MIME cryptographic signature


[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Index of Archives]     [Postgresql Jobs]     [Postgresql Admin]     [Postgresql Performance]     [Linux Clusters]     [PHP Home]     [PHP on Windows]     [Kernel Newbies]     [PHP Classes]     [PHP Books]     [PHP Databases]     [Postgresql & PHP]     [Yosemite]
  Powered by Linux