From: | Bruce Momjian <bruce(at)momjian(dot)us> |
---|---|
To: | Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at> |
Cc: | Edwin UY <edwin(dot)uy(at)gmail(dot)com>, pgsql-admin(at)lists(dot)postgresql(dot)org |
Subject: | Re: Create a Database or a Schema -- when to do what? |
Date: | 2025-02-20 23:33:40 |
Message-ID: | Z7e71MAepRvAxN38@momjian.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin |
On Fri, Feb 14, 2025 at 06:26:21AM +0100, Laurenz Albe wrote:
> On Fri, 2025-02-14 at 17:45 +1300, Edwin UY wrote:
> > When do you decide whether to create a database or a schema?
> > You can still create privs, access and security on the schema level, can't you?
>
> Yes, you can.
> However, the separation between databases is stronger.
> For example, some people take offence if others can see their metadata.
>
> My recommendation is to use different databases whenever you are
> dealing with distinct data sets and different applications.
> But if you have data sets that you routinely need to join,
> it is better to have them in a single database.
This blog post might help:
https://momjian.us/main/blogs/pgblog/2012.html#April_23_2012
--
Bruce Momjian <bruce(at)momjian(dot)us> https://momjian.us
EDB https://enterprisedb.com
Do not let urgent matters crowd out time for investment in the future.
From | Date | Subject | |
---|---|---|---|
Next Message | Jerry Sievers | 2025-02-21 03:57:43 | Re: In-place upgrade with streaming replicas |
Previous Message | Олег Самойлов | 2025-02-20 19:43:56 | Re: A trigger in an extension |