Re: Create a Database or a Schema -- when to do what?
От | kaido vaikla |
---|---|
Тема | Re: Create a Database or a Schema -- when to do what? |
Дата | |
Msg-id | CA+427g-aG5+t3Ss05bqegui0qW0yBJPDdYFGS5d6URKqP701nA@mail.gmail.com обсуждение исходный текст |
Ответ на | Re: Create a Database or a Schema -- when to do what? (Bruce Momjian <bruce@momjian.us>) |
Список | 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
br
Kaido
On Fri, 21 Feb 2025 at 01:33, Bruce Momjian <bruce@momjian.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@momjian.us> https://momjian.us
EDB https://enterprisedb.com
Do not let urgent matters crowd out time for investment in the future.
В списке pgsql-admin по дате отправления: