Обсуждение: Create a Database or a Schema -- when to do what?

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.

Yours,
Laurenz Albe

-- 

*E-Mail Disclaimer*
Der Inhalt dieser E-Mail ist ausschliesslich fuer den 
bezeichneten Adressaten bestimmt. Wenn Sie nicht der vorgesehene Adressat 
dieser E-Mail oder dessen Vertreter sein sollten, so beachten Sie bitte, 
dass jede Form der Kenntnisnahme, Veroeffentlichung, Vervielfaeltigung oder 
Weitergabe des Inhalts dieser E-Mail unzulaessig ist. Wir bitten Sie, sich 
in diesem Fall mit dem Absender der E-Mail in Verbindung zu setzen.

*CONFIDENTIALITY NOTICE & DISCLAIMER
*This message and any attachment are 
confidential and may be privileged or otherwise protected from disclosure 
and solely for the use of the person(s) or entity to whom it is intended. 
If you have received this message in error and are not the intended 
recipient, please notify the sender immediately and delete this message and 
any attachment from your system. If you are not the intended recipient, be 
advised that any use of this message is prohibited and may be unlawful, and 
you must not copy this message or attachment or disclose the contents to 
any other person.

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.