From: | kaido vaikla <kaido(dot)vaikla(at)gmail(dot)com> |
---|---|
To: | Bruce Momjian <bruce(at)momjian(dot)us> |
Cc: | Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at>, 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-28 19:07:33 |
Message-ID: | CA+427g-aG5+t3Ss05bqegui0qW0yBJPDdYFGS5d6URKqP701nA@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin |
To my developers i have described it using an excel example: do you need a
new excel file (new database) or a new sheet in excel (new schema)
br
Kaido
On Fri, 21 Feb 2025 at 01:33, Bruce Momjian <bruce(at)momjian(dot)us> wrote:
> 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 | Sbob | 2025-03-01 18:23:25 | fast way to run a query with 7 thousand constant values |
Previous Message | ek ek | 2025-02-28 16:37:59 | Re: Multi-MASTER across different locations |