pg.ddx.io pgsql-sql@postgresql.org mailing list archivehelp / color / mirror / Atom feed
From: Horst Herb <hherb@malleenet.net.au>
To: pgsql-sql@postgresql.org
Subject: Re: Diferent databases on same query...
Date: Sat, 27 Oct 2001 00:24:53 +1000
Message-ID: <20011026142041.24010.qmail@gnumed.dhs.org> (raw)
In-Reply-To: <22C9D178-C4E4-11D5-BBB1-003065C61C62@mac.com>
References: <22C9D178-C4E4-11D5-BBB1-003065C61C62@mac.com>
On Saturday 20 October 2001 08:53, you wrote:
> Andre,
>
> The only reason to have data for one query in different databases is if
> the databases are on different machines. If you're running on PC-type
> hardware, you might have to do that some times for performance reasons.
> But if at that point, you should ask yourself if you shouldn't invest in
> some faster hardware ;-).
There are many more good reasons to do so. Example from my own domain,
medicine:
1.) one database hold demographic information. This information is needed by
administration, nursing, and medical staff as well as by external service
providers such as pathology.
2.) another database holds medical information. The information here is
highly sensitive. The database admin should be a medical doctor,and it must
be unaccessible to clerical staff. SQL permissions are only a *very* weak
protection, not good enough for this purpose. For many good reasons, foremost
security, this information will not reside in the same database (sometimes
not even on the same machine) as the administrative data or the demographic
data.
3.) For obvious reasons, it would be bad to replicate the demographic data in
order to provide this data to administration, medical staff etc for their own
purposes.
Thus, we have multiple databases on multiple servers all depending on each
other. Some servers are read-only, others need the backend to log every
single query for audit trailing. The latter alone would blow the storage
needs out of proportion if applied to the whole set of databases. At present,
it is up to our client software to sort this out "manually". A minor
headache.
Horst
view thread (9+ messages) latest in thread
Message-ID: <20011026142041.24010.qmail@gnumed.dhs.org> Permalink: ../20011026142041.24010.qmail@gnumed.dhs.org/ Also on: postgresql.org/message-id/20011026142041.24010.qmail@gnumed.dhs.org ·
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-sql@postgresql.org Cc: hherb@malleenet.net.au Subject: Re: Diferent databases on same query... In-Reply-To: <20011026142041.24010.qmail@gnumed.dhs.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