Re: Create a Database or a Schema -- when to do what?

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



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

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





[Index of Archives]     [Postgresql Home]     [Postgresql General]     [Postgresql Performance]     [Postgresql PHP]     [Postgresql Jobs]     [PHP Users]     [PHP Databases]     [PHP Home]     [PHP on Windows]     [Kernel Newbies]     [PHP Classes]     [PHP Databases]     [Yosemite Forum]

  Powered by Linux