| From: | Thomas Kellerer <spam_eater(at)gmx(dot)net> |
|---|---|
| To: | pgsql-novice(at)postgresql(dot)org |
| Subject: | Re: One PostgreSQL server for multiple apps? |
| Date: | 2014-02-23 19:42:48 |
| Message-ID: | lediv8$afp$1@ger.gmane.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-novice |
Pandu Poluan wrote on 23.02.2014 16:37:
> I have been reading around, and it seems (CMIIW) that in PostgreSQL,
> a 'database' is similar to a SQL Server instance, while to create
> separate databases within an 'instance', I need to create 'schemas'.
>
> Am I reading this right?
I don't think so. "Databases" in SQL Server and Postgres are very similar.
The main difference is that in Postgres you can not do cross-database queries.
The schema concept inside a single database is more or less the same thing if we are talking about SQL Server 2008 and later.
I'm not familiar with SQL Server's instance concept but I would consider a Postgres "instance" a separate data directory ("cluster") with it's own set of processes listening on it's own port.
> There is another question, is it possible to limit the resources used
> by separate instances/databases so that different apps don't start to
> step on each others' toes?
No, I don't think this is currently possible with Postgres
| From | Date | Subject | |
|---|---|---|---|
| Next Message | amul sul | 2014-02-24 06:47:28 | SRF_RETURN_NEXT Error: rows returned by function are not all of the same row type |
| Previous Message | Sean Davis | 2014-02-23 17:28:58 | Re: One PostgreSQL server for multiple apps? |