From: | Pandu Poluan <pandu(at)poluan(dot)info> |
---|---|
To: | pgsql-novice(at)postgresql(dot)org |
Subject: | One PostgreSQL server for multiple apps? |
Date: | 2014-02-23 14:52:59 |
Message-ID: | CAA2qdGUpHzG2EU+oM8Ygh2LDBav5mTh6m9ZZCSRZgtHi=yYu=Q@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-novice |
Hello!
First, I apologize if this email sounds very... novice. I came from MS SQL
Server background, and am recently 'plunged' into a mid-to-long term
project to drop dependencies on proprietary databases, and use PostgreSQL
instead.
Now, in MS SQL Server, I can create a single server to service several apps
together. If the app is a light load and doesn't require something more
than db_owner privileges, I usually just clump them together in the Default
instance, using a new 'database'. If the app has heavier requirements, then
I would spin up a new instance, on the same server (provided RAM and IOPS
requirements suffice, of course).
How would the same principle be applied in PostgreSQL?
Thanks in advance for your kind guide.
Rgds,
--
From | Date | Subject | |
---|---|---|---|
Next Message | Sean Davis | 2014-02-23 15:28:12 | Re: One PostgreSQL server for multiple apps? |
Previous Message | Tom Lane | 2014-02-21 18:49:31 | Re: Re: Connection rejected: could not fork new process for connection: Unknown error |