[ADMIN] DBmirror

I would like to know whether I can set DBmirror replication from the fedora core 5_64 which postgresql8.1 was installed by rpm process not by compiling the source. All of the component include server, contrib, perl, test, doc, devel and lib were also rpm and what is the way to set it? Do I need to

Re: [ADMIN] DBmirror

Στις Δευτέρα 18 Δεκέμβριος 2006 11:55, ο/η [EMAIL PROTECTED] έγραψε: > I would like to know whether I can set DBmirror replication from the fedora > core 5_64 which postgresql8.1 was installed by rpm process not by compiling > the source. All of the component include server, contrib, perl, test, do

[ADMIN] DBmirror

I would like to know whether I can set DBmirror replication from the fedora core 5_64 which postgresql8.1 was installed by rpm process not by compiling the source. All of the component include server, contrib, perl, test, doc, devel and lib were also rpm and what is the way to set it? Do I need to

[ADMIN] DBmirror from 64 bit to 32 bit

I would like to know whether I could use two server for DBmirroring ,the master is 64 bit mechine with 64 bit linux X86-64 + postgresql 7.4.7 X86_64 and the other is slave and is the 32 bit mechine + Linux i386 + postgresql 7.4 i386 . Could these be run with DBmirror database replication ?

[ADMIN] DBmirror and 64 bit mechine

I would like to know whether I could use two server ,one as slave and it is the 32 bit mechine and Linux i386 + postgresql 7.4 i386 and the master is 64 bit mechine with 64 bit linux X86-64 and postgresql 7.4.7 X86_64 . Could these be run with DBmirror replication or what would be the expecte

[ADMIN] dbmirror modifies pg_proc nextval/setval functions

Title: dbmirror modifies pg_proc nextval/setval functions Hi all, I'm trying out dbmirror  for postgres 8.0.3 and I ran into some problems that I traced back to the setup sql script the MirrorSetup.sql, the standard nextval and setval get renamed using the following: UPDATE pg_proc SET pron

Re: [ADMIN] dbmirror modifies pg_proc nextval/setval functions

"James Doherty" <[EMAIL PROTECTED]> writes: > This changing of the name of what I would think is a pretty basic > function seems pretty risky. My, that *is* ugly isn't it? Not to mention that the replacement setval functions are created with the wrong argument datatypes. This looks exceedingly b

[ADMIN] dbmirror modifies pg_proc nextval/setval functions

Title: dbmirror modifies pg_proc nextval/setval functions Hi all, I'm trying out dbmirror  for postgres 8.0.3 and I ran into some problems that I traced back to the setup sql script, MirrorSetup.sql, the standard nextval and setval get renamed using the following: UPDATE pg_proc SET proname

Re: [ADMIN] dbmirror

bject:[ADMIN] dbmirror Hi I was wondering if anyone is using the dbmirror stuff that come with postgres versions >7.3.1. If so what kind of experiences have you had. I am looking a small number < 10 tables that will contain a lot of very important data and I would like a way to r

[ADMIN] dbmirror

Hi I was wondering if anyone is using the dbmirror stuff that come with postgres versions >7.3.1. If so what kind of experiences have you had. I am looking a small number < 10 tables that will contain a lot of very important data and I would like a way to replicate it. Thanks Edward -

Re: [ADMIN] DBMirror - Replicating binary objects of type bytea ?

On Wed, Aug 20, 2003 at 05:34:26PM +0200, VanderLeeden wrote: > Second question: Is a "manual" failover setup possible and > recommended using DBMirror? I haven't used dbmirror, but I would never[1] fail over automatically from an asynchronous system. Some suggestions on fail over: 1. Make

[ADMIN] DBMirror - Replicating binary objects of type bytea ?

Anyone has a clue of why the replication using DBMirror (PostgreSQL 7.3.4) does not replicate correctly if the primary key is of type "bytea" ? Error message from  DBMirror.pl  is e.g.   ERROR:  Cannot insert a duplicate key into unique index payment_pkey   Second question:  Is a "manual" fa

[ADMIN] dbmirror and failure/recovery modes

Dear peoples, I'm setting up a database in postgres which will have light traffic writing to a few tables (and somewhat heavier traffic reading them). We'd like to mirror that databse using dbmirror to two others. Let's assume that we're humming along and the master goes down. We switch traffic

[ADMIN] dbmirror install

hello, if anyone has experience with dbmirror.pl please advise: I am installing dbmirror (from contrib tree): I compiled it under the source tree of postgresql-7.3b2 and everything went fine: since I need to test it on a postgres-7.1.3 installation (which does not include dbmirror) I then copie

Re: [ADMIN] [DBmirror Issue] recordchange() dies in packageData unless

Patch withdrawn by author. Newer version already applied. --- Steven Singer wrote: > On Mon, 23 Sep 2002, Rajesh Kumar Mallah. wrote: > > > Hi > > > > Is anyone using dbmirror in production? > > We've been using it in

Re: [ADMIN] [DBmirror Issue] recordchange() dies in packageData unless

Your patch has been added to the PostgreSQL unapplied patches list at: http://candle.pha.pa.us/cgi-bin/pgpatches I will try to apply it within the next 48 hours. --- Steven Singer wrote: > On Mon, 23 Sep 2002, Ra

Re: [ADMIN] [DBmirror Issue] recordchange() dies in packageData unless

On Mon, 23 Sep 2002, Rajesh Kumar Mallah. wrote: > Hi > > Is anyone using dbmirror in production? We've been using it in production for sometime now and haven't been having any problems with it. > > I Intend to replicate a set of tables between local and remote servers. > and plan to use

Re: [ADMIN] [DBmirror Issue] recordchange() dies in packageData unless there is a PRIMARY KEY on DELETE and UPDATEs.

Hi Steven, Your most recent version pending.c does not crashes postmaster anymore when PRIMARY KEYS are missing. Instead it raises notices and errors: tradein_clients=> BEGIN work; UPDATE iid_listing set city='DELHI testing' where list_id=23312; BEGIN NOTICE: Could not select primary index key

Re: [ADMIN] [DBmirror Issue] recordchange() dies in packageData unless there is a PRIMARY KEY on DELETE and UPDATEs.

"Rajesh Kumar Mallah." <[EMAIL PROTECTED]> writes: > # patch -p0 < patch > patch: malformed patch at line 7: PRIMARY); I think the patch got mucked up by line-wrapping, either in your mail program or Steve's ... regards, tom lane ---(end of

Re: [ADMIN] [DBmirror Issue] recordchange() dies in packageData unless there is a PRIMARY KEY on DELETE and UPDATEs.

[Rajesh Kumar Mallah] > Hi can you help me with applying the patch > i dunno much abt patch > > # patch -p0 < patch > patch: malformed patch at line 7: PRIMARY); It looks like a context patch. patch --help should tell you how to apply a context patch. It will also tell you the basic syntax

Re: [ADMIN] [DBmirror Issue] recordchange() dies in packageData unless there is a PRIMARY KEY on DELETE and UPDATEs.

Hi can you help me with applying the patch i dunno much abt patch # patch -p0 < patch patch: malformed patch at line 7: PRIMARY); regds mallah. On Tuesday 24 September 2002 02:18, Steven Singer wrote: > On Mon, 23 Sep 2002, Rajesh Kumar Mallah. wrote: > > Hi > > > > Is anyone using

Re: [ADMIN] [DBmirror Issue] recordchange() dies in packageData unless there is a PRIMARY KEY on DELETE and UPDATEs.

Hi Steven , thanks for the reply and letting me know that a primary key is essential for the replicated tables. For your information pending.c used to crash postmaster even when it was not in debug mode. (it was only then i defined DEBUG_OUTPUT to see whats going on). Thanks for the patch. But

[ADMIN] [DBmirror Issue] recordchange() dies in packageData unless there is a PRIMARY KEY on DELETE and UPDATEs.

Hi Is anyone using dbmirror in production? I Intend to replicate a set of tables between local and remote servers. and plan to use dbmirror. I observe that unless a table has a primary key the trigger recordchange() which is supposed to be attached to a replicated table does not works properly