pg.ddx.io  pgsql-admin@postgresql.org mailing list archive  

help / color / mirror / Atom feed

From: Christian Ullrich <chris@chrullrich.net>
To: pgsql-admin@postgresql.org
Subject: Re: Creating schema best practices
Date: Fri, 05 Oct 2012 17:07:57 +0200
Message-ID: <k4mt4o$g0b$3@ger.gmane.org> (raw)
In-Reply-To: <C6B1B26CA32AC64F8274F7ACE29D61732F56EA8C@G4W3297.americas.hpqcorp.net>
References: <C6B1B26CA32AC64F8274F7ACE29D61732F567DE0@G9W0745.americas.hpqcorp.net>
	<CAFwQ8rewYJhNCWWyaZaNDR5X9yMVxz_zLL0Up_ik0sgQ8g+g9w@mail.gmail.com>
	<C6B1B26CA32AC64F8274F7ACE29D61732F56EA8C@G4W3297.americas.hpqcorp.net>

* 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.

-- 
Christian

view thread (6+ messages)  latest in thread

Message-ID: <k4mt4o$g0b$3@ger.gmane.org>
Permalink:  ../k4mt4o$g0b$3@ger.gmane.org/
Also on:    postgresql.org/message-id/k4mt4o$g0b$3@ger.gmane.org

copy link · copy postgr.es

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: pgsql-admin@postgresql.org
  Cc: chris@chrullrich.net
  Subject: Re: Creating schema best practices
  In-Reply-To: <k4mt4o$g0b$3@ger.gmane.org>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox