agora inbox for pgsql-admin@postgresql.org
help / color / mirror / Atom feedCreate a Database or a Schema -- when to do what?
4+ messages / 4 participants
[nested] [flat]
* Create a Database or a Schema -- when to do what?
@ 2025-02-14 04:45 Edwin UY <edwin.uy@gmail.com>
0 siblings, 1 reply; 4+ messages in thread
From: Edwin UY @ 2025-02-14 04:45 UTC (permalink / raw)
To: pgsql-admin@lists.postgresql.org
Hi.
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?
^ permalink raw reply [nested|flat] 4+ messages in thread
* Re: Create a Database or a Schema -- when to do what?
@ 2025-02-14 05:26 Laurenz Albe <laurenz.albe@cybertec.at>
parent: Edwin UY <edwin.uy@gmail.com>
0 siblings, 1 reply; 4+ messages in thread
From: Laurenz Albe @ 2025-02-14 05:26 UTC (permalink / raw)
To: Edwin UY <edwin.uy@gmail.com>; pgsql-admin@lists.postgresql.org
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.
^ permalink raw reply [nested|flat] 4+ messages in thread
* Re: Create a Database or a Schema -- when to do what?
@ 2025-02-20 23:33 Bruce Momjian <bruce@momjian.us>
parent: Laurenz Albe <laurenz.albe@cybertec.at>
0 siblings, 1 reply; 4+ messages in thread
From: Bruce Momjian @ 2025-02-20 23:33 UTC (permalink / raw)
To: Laurenz Albe <laurenz.albe@cybertec.at>; +Cc: Edwin UY <edwin.uy@gmail.com>; pgsql-admin@lists.postgresql.org
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.
^ permalink raw reply [nested|flat] 4+ messages in thread
* Re: Create a Database or a Schema -- when to do what?
@ 2025-02-28 19:07 kaido vaikla <kaido.vaikla@gmail.com>
parent: Bruce Momjian <bruce@momjian.us>
0 siblings, 0 replies; 4+ messages in thread
From: kaido vaikla @ 2025-02-28 19:07 UTC (permalink / raw)
To: Bruce Momjian <bruce@momjian.us>; +Cc: Laurenz Albe <laurenz.albe@cybertec.at>; Edwin UY <edwin.uy@gmail.com>; pgsql-admin@lists.postgresql.org
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@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.
>
>
>
^ permalink raw reply [nested|flat] 4+ messages in thread
end of thread, other threads:[~2025-02-28 19:07 UTC | newest]
Thread overview: 4+ messages (download: mbox mbox.gz follow: Atom feed)
-- links below jump to the message on this page --
2025-02-14 04:45 Create a Database or a Schema -- when to do what? Edwin UY <edwin.uy@gmail.com>
2025-02-14 05:26 ` Laurenz Albe <laurenz.albe@cybertec.at>
2025-02-20 23:33 ` Bruce Momjian <bruce@momjian.us>
2025-02-28 19:07 ` kaido vaikla <kaido.vaikla@gmail.com>
This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox