pg.ddx.io  pgsql-testers@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Craig Ringer <ringerc@ringerc.id.au>
To: Ivan Sergio Borgonovo <mail@webthatworks.it>
Cc: pgsql-general@postgresql.org
Subject: Re: Pg multi-tenanted hard? was: FREE hosting platforms with PostgreSQL, Java SDK, Tomcat, ecc.?
Date: Mon, 08 Aug 2011 05:38:02 +0800
Message-ID: <4E3F05BA.6010708@ringerc.id.au> (raw)
In-Reply-To: <20110807174337.69848d17@dawn.webthatworks.it>
References: <CA+rcckxD6BBWjuw=1yJNyQvsvS4En+Fd88Q7JacbKXj0es6S1w@mail.gmail.com>
	<4E3E87F7.7040001@ringerc.id.au>
	<20110807174337.69848d17@dawn.webthatworks.it>

On 7/08/2011 11:43 PM, Ivan Sergio Borgonovo wrote:
> On Sun, 07 Aug 2011 20:41:27 +0800
> Craig Ringer<ringerc@ringerc.id.au>  wrote:
>
>> By the way, one of the reasons you're not finding much free
>> hosting for PostgreSQL is that it takes a fair bit of work to run
>> Pg multi-tenanted. Your additional requirement for Java and Tomcat
> Why should pg be harder than anything else?

Before I go on: I'm not running a hosting provider. Most of this is 
gathered from time on the lists, plus my own observations from using Pg 
in situations where I want to prevent different apps sharing a DB from 
affecting each other. Given that qualification:

Things that contribute to making it harder to offer multi-tenanted 
database hosting services with Pg include: The global catalogs, in 
particular global user lists; relatively limited options for automatic 
load limitation and prioritisation; difficulty of preventing certain 
classes of effective denial of service by authorized users; shared WAL 
making it harder to isolate load and limit one DB's effects on another; 
difficulties completely hiding users from each other; the need to tune 
autovacuum to make sure it keeps up with load; etc. In Pg, DBs in a 
cluster affect each other in various ways, but because of the 
pinned-in-RAM nature of shared_buffers its hard to run one cluster per 
user as would be ideal.

This doesn't mean you can't use Pg for multi-tenanted DB hosting. It 
just makes it harder, and means its more sysadmin work, therefore more 
time and cost.

There are DBs - mostly $OMFGLOTS DBs - that offer much greater 
facilities for controlling access and isolating load than Pg does and 
are better suited to multi-tenanted use. Of course, their costs are such 
that it's probably cheaper to hire an army of sysadmins to run a giant 
cluster of Pg boxes instead...

--
Craig Ringer



view thread (3+ messages)  latest in thread

Message-ID: <4E3F05BA.6010708@ringerc.id.au>
Permalink:  ../4E3F05BA.6010708@ringerc.id.au/
Also on:    postgresql.org/message-id/4E3F05BA.6010708@ringerc.id.au

 · 

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-testers@postgresql.org
  Cc: ringerc@ringerc.id.au, mail@webthatworks.it, pgsql-general@postgresql.org
  Subject: Re: Pg multi-tenanted hard? was: FREE hosting platforms with PostgreSQL, Java SDK, Tomcat, ecc.?
  In-Reply-To: <4E3F05BA.6010708@ringerc.id.au>
  References: <CA+rcckxD6BBWjuw=1yJNyQvsvS4En+Fd88Q7JacbKXj0es6S1w@mail.gmail.com> <4E3E87F7.7040001@ringerc.id.au> <20110807174337.69848d17@dawn.webthatworks.it> <4E3F05BA.6010708@ringerc.id.au>

* 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