Обсуждение: Postgres replication

Dear All

I have a application running at various locations with backend as postgres
Slony is configured at all locations for replication at local site anda central server where each site has its own database instance.

Now we wish to merge data collected from all the sites into one database instance to provide consolidated view

database schema is same at all the places
However as the application is still under development the schema maychange. however the change will happen at all the locations.

Pls suggest a solution

with regards


Nalini S. Nautiyal

On Thursday 10 January 2008 00:38:38 nalini wrote:
> Dear All
>
> I have a application running at various locations with backend as postgres
> Slony is configured at all locations for replication at local site anda
> central server where each site has its own database instance.
>
> Now we wish to merge data collected from all the sites into one database
> instance to provide consolidated view
>
> database schema is same at all the places
> However as the application is still under development the schema maychange.
> however the change will happen at all the locations.
>
> Pls suggest a solution
>
> with regards
>
>
> Nalini S. Nautiyal

Maybe you could use dblink (in contribs) or dbi-link (see pgfoundry) and
create a db full of remote "views" each one being a join that retrieves all
data for that table from all related databases/clusters ?

/Kevin

On Jan 10, 2008 1:38 AM, nalini <nalini@nic.in> wrote:
> Dear All
>
> I have a application running at various locations with backend as postgres
> Slony is configured at all locations for replication at local site anda
> central server where each site has its own database instance.
>
> Now we wish to merge data collected from all the sites into one database
> instance to provide consolidated view
>
> database schema is same at all the places
> However as the application is still under development the schema maychange.
> however the change will happen at all the locations.

I would replicate each one to a different schema on the same server
and then use views to consolidate the data into what appears to be one
set.  To make everything unique, you could prepend a unique id to each
identifier based on the schema it came from.

Thanks for the suggestion. I would still like to know whether we have any tools available in open source domain for the same. Handling views may become difficult due to size and complexity of the database




----- Original Message -----
From: Scott Marlowe <scott.marlowe@gmail.com>
Date: Thursday, January 10, 2008 8:48 pm
Subject: Re: [ADMIN] Postgres replication
To: nalini <nalini@nic.in>
Cc: pgsql-admin@postgresql.org

> On Jan 10, 2008 1:38 AM, nalini <nalini@nic.in> wrote:
> > Dear All
> >
> > I have a application running at various locations with backend
> as postgres
> > Slony is configured at all locations for replication at local
> site anda
> > central server where each site has its own database instance.
> >
> > Now we wish to merge data collected from all the sites into
> one database
> > instance to provide consolidated view
> >
> > database schema is same at all the places
> > However as the application is still under development the
> schema maychange.
> > however the change will happen at all the locations.
>
> I would replicate each one to a different schema on the same server
> and then use views to consolidate the data into what appears to
> be one
> set.  To make everything unique, you could prepend a unique
> id to each
> identifier based on the schema it came from.
>
> ---------------------------(end of broadcast)--------------------
> -------
> TIP 6: explain analyze is your friend

Nalini S. Nautiyal