Re: PostgreSQL - case studies

On Wed, Feb 10, 2010 at 9:39 AM, Jayadevan M
<Jayadevan(dot)Maymala(at)ibsplc(dot)com>wrote:

> Any feedback - a few sentences with the db size, tps, h/w necessary to
> support that, and acceptable down-time, type of application etc will be
> greatly appreciated.
> Our products are not of the blog/social networking type, but more of
> on-line reservation type where half an hour down-time can lead to
> significant revenue losses for customers.
> Thank you,
> Jayadevan
>
>
I don't have experience with DB size greater than 25-26 GB at the moment,
but Postgres surely has no problems handling my requirements. Mind you,
this Was on a stock Postgresql server running on FreeBSD 7.x without any
optimizations. Didn't seen any downtime apart from the ones that I goofed
up. H/w config was dual processor Xeon/8GB RAM and a single SAS 15K disk
(146 GB). The rig has been upgraded last week, but it ran fine for more than
18 months.

That said, we run an application which generates around 170-200 transactions
per second (mix of select insert, update and delete). AFAIK, most of us
using Postgres are running some or the other critical application where
downtime has a significant cost attached to it.

With regards

Amitabh