Date: Thu, 20 Feb 2025 18:33:40 -0500
From: Bruce Momjian <bruce@momjian.us>
To: Laurenz Albe <laurenz.albe@cybertec.at>
Cc: Edwin UY <edwin.uy@gmail.com>, pgsql-admin@lists.postgresql.org
Subject: Re: Create a Database or a Schema -- when to do what?
Message-ID: <Z7e71MAepRvAxN38@momjian.us>
References: 
 <CA+wokJ9Ofq1brmo_EKVm9_=eEEWVGpSjaR8NAh+NsDTbpLxnFg@mail.gmail.com>
 <eab7096c9dee64e71842a85a0fde359fc10a8ab0.camel@cybertec.at>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <eab7096c9dee64e71842a85a0fde359fc10a8ab0.camel@cybertec.at>
Archived-At: 
 <https://www.postgresql.org/message-id/Z7e71MAepRvAxN38%40momjian.us>
Precedence: bulk

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@momjian.us>        https://momjian.us
  EDB                                      https://enterprisedb.com

  Do not let urgent matters crowd out time for investment in the future.