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

From: snacktime <snacktime(at)gmail(dot)com>
To: "pgsql-general(at)postgresql(dot)org" <pgsql-general(at)postgresql(dot)org>
Subject: Re: [Slony1-general] Using slony with many schema's
Date: 2006-10-11 18:55:48
Message-ID: 1f060c4c0610111155y34abe249w1871acc58f2b8467@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

First, thanks for all the feedback. After spending some more time
evaluating what we would gain by using slony I'm not sure it's worth
it. However I thought I would get some more feedback before
finalizing that decision.

The primary reason for looking at replication was to move cpu
intensive SELECT queries to a slave. However, by moving away from
schema's the report queries for all clients on the server become more
cpu intensive instead of just the clients with large data sets. The
average distribution is that 95% of our clients have less then 5000
rows in any table, and the other 5% can have hundreds of thousands.
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.

Chris

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Rafal Pietrak 2006-10-11 18:56:23 Re: STABLE functions
Previous Message J S B 2006-10-11 18:50:59 invalid data in PID file