Skip site navigation (1) Skip section navigation (2)

Re: Creating schema best practices

From: Christian Ullrich <chris(at)chrullrich(dot)net>
To: pgsql-admin(at)postgresql(dot)org
Subject: Re: Creating schema best practices
Date: 2012-10-05 15:07:57
Message-ID: k4mt4o$g0b$ (view raw, whole thread or download thread mbox)
Lists: pgsql-admin
* Babay Adi, Hava wrote:

> On the same regard – Some of the mentioned modules in the mentioned
> application use a set of tables which is logically separate (there are
> no join statements with tables of other modules). What are the pros\cons
> of using a separate database instead of a separate schema for
> maintaining such tables?

For one thing, with multiple databases you cannot easily take consistent 
backups using pg_dump, because a transaction is local to a single database.


In response to

pgsql-admin by date

Next:From: Gl VmDate: 2012-10-05 16:19:00
Subject: Promoting a Cascading Standby
Previous:From: Stephen FrostDate: 2012-10-04 01:18:03
Subject: Re: Migrating to PG 9.2 (LONG, SORRY)

Privacy Policy | About PostgreSQL
Copyright © 1996-2017 The PostgreSQL Global Development Group