Thread: Cross Platform Continous Archiving and Replication

Cross Platform Continous Archiving and Replication

From
Selva manickaraja
Date:
Hi,

We are in the process of setting up
(a) Continous Archiving between machineA and machine B (Both Linux)
(b) Replication between machineA and machineC (Both Linux)
(c) Continous Archiving between machineA and machineD (Linux and Windows)

We got the (a) and (b) working and are in trial mode. We are not sure if (c) will work between different OS. Any clues or opinion on how we should approach this.

Thank you.

Warmest Regards,

Selvam

Re: Cross Platform Continous Archiving and Replication

From
Devrim GÜNDÜZ
Date:
On Thu, 2011-02-10 at 16:39 +0800, Selva manickaraja wrote:
> We are in the process of setting up
> (a) Continous Archiving between machineA and machine B (Both Linux)
> (b) Replication between machineA and machineC (Both Linux)
> (c) Continous Archiving between machineA and machineD (Linux and
> Windows)
>
> We got the (a) and (b) working and are in trial mode. We are not sure
> if (c) will work between different OS. Any clues or opinion on how we
> should approach this.

WAL replication won't work between different OS'es, and between
different arches. It even won't work between different Linux flavors.
You need to use a replication solution, like Slony.

Regards,
--
Devrim GÜNDÜZ
EnterpriseDB: http://www.enterprisedb.com
PostgreSQL Danışmanı/Consultant, Red Hat Certified Engineer
Community: devrim~PostgreSQL.org, devrim.gunduz~linux.org.tr
http://www.gunduz.org  Twitter: http://twitter.com/devrimgunduz

Attachment

Re: Cross Platform Continous Archiving and Replication

From
Selva manickaraja
Date:
I am using Postgresql 9.0 with its native replication and continous archiving. As per my understanding the primary and secondary communication via log files for continous archiving and direct postgres engine to engine communication for replication. These should not be a problem since I can use the pgadmin_III in Windows to perform transaction in the postgresql database residing on RedHat. Please clarify.

2011/2/10 Devrim GÜNDÜZ <devrim@gunduz.org>
On Thu, 2011-02-10 at 16:39 +0800, Selva manickaraja wrote:
> We are in the process of setting up
> (a) Continous Archiving between machineA and machine B (Both Linux)
> (b) Replication between machineA and machineC (Both Linux)
> (c) Continous Archiving between machineA and machineD (Linux and
> Windows)
>
> We got the (a) and (b) working and are in trial mode. We are not sure
> if (c) will work between different OS. Any clues or opinion on how we
> should approach this.

WAL replication won't work between different OS'es, and between
different arches. It even won't work between different Linux flavors.
You need to use a replication solution, like Slony.

Regards,
--
Devrim GÜNDÜZ
EnterpriseDB: http://www.enterprisedb.com
PostgreSQL Danışmanı/Consultant, Red Hat Certified Engineer
Community: devrim~PostgreSQL.org, devrim.gunduz~linux.org.tr
http://www.gunduz.org  Twitter: http://twitter.com/devrimgunduz

mapping libraries

From
Fabricio
Date:

Hi...

If i can't upgrade a server with postgres 8.1 and at this time i can't delete a super user, Is there any way to avoid that the super user mapping libraries in C code? like system y libc.so ?

regards...

Re: mapping libraries

From
Fabricio
Date:
Any comment about this?

Regards...



From: fabrixio1@hotmail.com
To: pgsql-admin@postgresql.org
Subject: [ADMIN] mapping libraries
Date: Thu, 10 Feb 2011 18:19:33 -0700

.ExternalClass .ecxhmmessage P {padding:0px;} .ExternalClass body.ecxhmmessage {font-size:10pt;font-family:Tahoma;}
Hi...

If i can't upgrade a server with postgres 8.1 and at this time i can't delete a super user, Is there any way to avoid that the super user mapping libraries in C code? like system y libc.so ?

regards...

Re: mapping libraries

From
Gerhard Hintermayer
Date:
What exactly do you mean ? Upgrade libraries which postgres depends on
while the server is running ? Depends on the distro I think. I did
this with gentoo, e.g. upgrade glibc while postgres (and other
services) still use the old version. Except from memory issues (both
versions have to be kept in memory) there should'nt be a problem. Next
time postmaster is started (and hopefully does start :-) ) the new
libraries will be used.

Gerhard

On Tue, Feb 15, 2011 at 6:34 AM, Fabricio <fabrixio1@hotmail.com> wrote:
> Any comment about this?
>
> Regards...
>
>
> ________________________________
> From: fabrixio1@hotmail.com
> To: pgsql-admin@postgresql.org
> Subject: [ADMIN] mapping libraries
> Date: Thu, 10 Feb 2011 18:19:33 -0700
>
>
> Hi...
> If i can't upgrade a server with postgres 8.1 and at this time i can't
> delete a super user, Is there any way to avoid that the super user mapping
> libraries in C code? like system y libc.so ?
> regards...
>

Re: mapping libraries

From
Fabricio
Date:


no no no... is not about upgrade libraries, is about  a  super user  failing to "create function ... language c" and with this avoid a super user gets a shell creating the function "system()" in the libc.so. In postgres 8.2 every library intented for use with postgres must carry a magic block to identify itself, but for the moment a can't upgrade a server. 
I know this is very old but is just a question :). 
I think the only way is updrade and not use super users, but if I upgrade and I need a super user for load data with copy command and this is a operating system user too for upload de data to the server, What avoid that the user load libraries like system() with the magic block and gets access to the cluster database with user postgres?

thank  Gerhard

regards...                                                                                                                                                                                              

> Date: Tue, 15 Feb 2011 08:10:14 +0100
> Subject: Re: [ADMIN] mapping libraries
> From: gerhard.hintermayer@gmail.com
> To: pgsql-admin@postgresql.org
>
> What exactly do you mean ? Upgrade libraries which postgres depends on
> while the server is running ? Depends on the distro I think. I did
> this with gentoo, e.g. upgrade glibc while postgres (and other
> services) still use the old version. Except from memory issues (both
> versions have to be kept in memory) there should'nt be a problem. Next
> time postmaster is started (and hopefully does start :-) ) the new
> libraries will be used.
>
> Gerhard
>
> On Tue, Feb 15, 2011 at 6:34 AM, Fabricio <fabrixio1@hotmail.com> wrote:
> > Any comment about this?
> >
> > Regards...
> >
> >
> > ________________________________
> > From: fabrixio1@hotmail.com
> > To: pgsql-admin@postgresql.org
> > Subject: [ADMIN] mapping libraries
> > Date: Thu, 10 Feb 2011 18:19:33 -0700
> >
> >
> > Hi...
> > If i can't upgrade a server with postgres 8.1 and at this time i can't
> > delete a super user, Is there any way to avoid that the super user mapping
> > libraries in C code? like system in libc.so ?
> > regards...
> >
>
> --
> Sent via pgsql-admin mailing list (pgsql-admin@postgresql.org)
> To make changes to your subscription:
> http://www.postgresql.org/mailpref/pgsql-admin