From: Rod Taylor <pg@rbt.ca>
To: Joel Fradkin <jfradkin@wazagua.com>
Cc: PostgreSQL Perform <pgsql-performance@postgresql.org>
Subject: Re: Final decision
Date: Wed, 27 Apr 2005 11:23:43 -0400
Message-ID: <1114615423.77587.175.camel@home> (raw)
In-Reply-To: <000001c54b3a$054d3720$797ba8c0@jfradkin>
References: <000001c54b3a$054d3720$797ba8c0@jfradkin>
>
> I did have a question if any folks are using two servers one for
> reporting and one for data entry what system should be the beefier?
Yeah. We started putting up slaves for reporting purposes and
application specific areas using Slony replicating partial data sets to
various locations -- some for reporting.
If your reports have a long runtime and don't require transactional
safety for writes (daily summary written or results aren't recorded in
the DB at all) this is probably something to consider.
I understand that PGAdmin makes Slony fairly painless to setup, but it
can be time consuming to get going and Slony can add new complications
depending on the data size and what you're doing with it -- but they're
working hard to reduce the impact of those complications.
> I have a 2proc machine I will be using and I can either put Sears off
> by themselves on this machine or split up functionality and have one
> for reporting and one for inserts and updates; so not sure which
> machine would be best for which spot (reminder the more robust is a
> 4proc with 8 gigs and 2 proc is 4 gigs, both dells).
>
>
>
> Thank you for any ideas in this arena.
>
>
>
> Joel Fradkin
>
>
>
>
>
>
>
>
>
--
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-performance@postgresql.org
Cc: pg@rbt.ca, jfradkin@wazagua.com
Subject: Re: Final decision
In-Reply-To: <1114615423.77587.175.camel@home>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox