Re: exporting data from one DB to another asynchronously - Mailing list pgsql-novice

It's relatively straightforward (ie well documented) to implement a
web application with a database on the same machine or even on a
different machine.

But I think if you have two or three applications that access subsets
of the same data and it is private information (with penalties for any
unwanted data disclosures) and you want it to be as secure as possible
then it is much less simple.

Someone suggested that I have a single Postgres instance with three
tablespaces. If I have a separate machine running the Postgres DB and
three applications accessing only the tables in their respective
tablespace that may be easier and more secure to implement.

It seems there is a way to migrate data between tablespaces with
stored procedures and triggers and not have the application themselves
be aware of the requirements of the others.

This way I only have to worry about one database but any failure in
that will bring down all three apps.

Thanks,
NK





On 3/5/06, John Purser <jmpurser@gmail.com> wrote:
> On Sun, 5 Mar 2006 14:20:09 -0800
> "Nagita Karunaratne" <nagita.k@gmail.com> wrote:
>
> > Hi John,
> >
> > I think I over-elaborated.
> >
> > Basically I would like to know if postgresql can move information from
> > one instance to another periodically (daily).
> >
> > So if the source database has customer name, address, phone, model
> > purchased, date of purchase, color etc.
> >
> > Can it move just the date of purchase, model, color to a second
> > database in another application so it is ready when they login to that
> > application to take a after sales survey?
> >
> > Thanks,
> > NK
> >
> > ---------------------------(end of
> > broadcast)--------------------------- TIP 1: if posting/reading
> > through Usenet, please send an appropriate subscribe-nomail command
> > to majordomo@postgresql.org so that your message can get through to
> > the mailing list cleanly
>
> Nagita,
>
> I say this without mailice or spite.  You seem to be a person who knows
> nothing of dance or carpentry but you're asking me if this dance floor
> can do the jitterbug.
>
> Postgresql, the database (or the floor) holds your data.  The End.  A
> database APPLICATION can move data back and forth from one database to
> another (or more likely I think in this case) present the information
> in a variety of ways by asking the database for it.  Now postgres has
> tools built into it which can do a lot of things but it takes a dancer
> to use it.  Think of it as having the steps to a variety of dances
> painted into the dance floor.
>
> I hope this terribly strained metaphor makes it a bit clearer.  And
> honestly I am not attempting to ridicule you!  Some full time
> computer programmers (and an ungodly number of wanna be's) have no
> clearer idea of what a database does.
>
> John
> --
> You've been leading a dog's life.  Stay off the furniture.
>