pg.ddx.io  pgsql-performance@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: tsuraan <tsuraan@gmail.com>
To: pgsql-performance@postgresql.org
Subject: Re: Scaling concerns
Date: Sun, 17 Dec 2006 15:59:11 -0600
Message-ID: <84fb38e30612171359r6288de69y2553be256019ba4b@mail.gmail.com> (raw)
In-Reply-To: <20061217032527.GL29195@andi-lap.la.revver.com>
References: <84fb38e30612160926l609ec55cs352b2495289bae0c@mail.gmail.com>
	<20061217032527.GL29195@andi-lap.la.revver.com>

> For scaling you should consider slony. Either hangout on #slony on
> Freenode.net or ask on the mailing list if you have questions.

For some reason I had thought slony was really immature, but it
actually looks really usable.

> Intel chips => define more. There are Intel boxes known to have issues
> under specific load scenarios with PostgreSQL (again specific
> versions). To make it funnier, these are really really hard to track
> down ;)

I can't access the Intel machine right now, but it's the current
fastest Intel dual-core.  I'll figure it out tomorrow.

> Cluster. One box that applies changes, and multiple boxes that read
> the data.
>
> If you cannot afford multiple boxes from the start, design your
> application still to work with two connections: one connection to a
> user with read/write permissions, and one connecting to a user having
> only select permissions => this way you can later easily add a
> loadbalancer to the mix, and use multiple postgres boxes for reading
> stuff.

I think I'll see what I can do for that.  Is there an aggregation-type
of clustering for Postgres?  I'm thinking of something where database
information is divided between machines, rather than shared among them
as in Slony.  Sort of like the difference between RAID0 and RAID1.
Since my application is constantly adding to the database (far more is
written than is ever read), it would be nice to have a multiple-write,
single reader solution, if such a thing exists.



view thread (12+ messages)  latest in thread

Message-ID: <84fb38e30612171359r6288de69y2553be256019ba4b@mail.gmail.com>
Permalink:  ../84fb38e30612171359r6288de69y2553be256019ba4b@mail.gmail.com/
Also on:    postgresql.org/message-id/84fb38e30612171359r6288de69y2553be256019ba4b@mail.gmail.com

 · 

reply

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 from your mail client; the link fills in
  the headers below: reply via email
  Some clients, webmail especially, drop In-Reply-To and References from
  a link, and the reply then starts a new thread: use the mbox below.

  To: pgsql-performance@postgresql.org
  Cc: tsuraan@gmail.com
  Subject: Re: Scaling concerns
  In-Reply-To: <84fb38e30612171359r6288de69y2553be256019ba4b@mail.gmail.com>
  References: <84fb38e30612160926l609ec55cs352b2495289bae0c@mail.gmail.com> <20061217032527.GL29195@andi-lap.la.revver.com> <84fb38e30612171359r6288de69y2553be256019ba4b@mail.gmail.com>

* 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