Skip site navigation (1) Skip section navigation (2)

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

From: Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>
To: Steven Singer <ssinger(at)navtechinc(dot)com>
Cc: "Rajesh Kumar Mallah(dot)" <mallah(at)trade-india(dot)com>,pgsql-admin(at)postgresql(dot)org, pgsql-replication(at)postgresql(dot)org
Subject: Re: [DBmirror Issue] recordchange() dies in packageData unless
Date: 2002-09-29 03:24:05
Message-ID: 200209290324.g8T3O5K16601@candle.pha.pa.us (view raw or flat)
Thread:
Lists: pgsql-admin
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, 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 dbmirror.
> > 
> 
> The speed of replicating edits over a WAN isn't that great.  
> If you perform a lot of edits in a short period of time there could be a 
> backlog. 
> 
> > 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
> > and causes postmaster to crash.
> > 
> 
> dbmirror requires that all tables that you replicate have primary 
> keys(This should be said more explictly in the README)
> 
> However it still should not crash(In defence it will only crash the 
> postmaster when you compile dbmirror in debug mode).  
> 
> The attatched patch to pending.c should prevent it from crashing the 
> postmaster.  Let me know if it fixes the problem and I'll submit it to 
> pgpatches.
> 
> 
> *** pending.c	Mon Sep 23 20:24:04 2002
> --- /tmp/pending.c	Mon Sep 23 20:23:43 2002
> ***************
> *** 226,232 ****
>   	/* pplan = SPI_saveplan(pplan); */
>   	cpKeyData = packageData(tTupleData, tTupleDesc, tpTrigData, 
> PRIMARY);
>   #if defined DEBUG_OUTPUT
> ! 	elog(NOTICE, cpKeyData);
>   #endif
>   	saPlanData[0] = PointerGetDatum(cpKeyData);
>   
> --- 226,235 ----
>   	/* pplan = SPI_saveplan(pplan); */
>   	cpKeyData = packageData(tTupleData, tTupleDesc, tpTrigData, 
> PRIMARY);
>   #if defined DEBUG_OUTPUT
> ! 	if(cpKeyData != NULL ) 
> ! 	{
> ! 		elog(NOTICE, cpKeyData);
> ! 	}
>   #endif
>   	saPlanData[0] = PointerGetDatum(cpKeyData);
>   
> 
> 
> 
> 
> -- 
> Steven Singer                                       ssinger(at)navtechinc(dot)com
> Aircraft Performance Systems                Phone:  519-747-1170 ext 282
> Navtech Systems Support Inc.                AFTN:   CYYZXNSX SITA: YYZNSCR
> Waterloo, Ontario                           ARINC:  YKFNSCR
> 
> 
> ---------------------------(end of broadcast)---------------------------
> TIP 4: Don't 'kill -9' the postmaster
> 

-- 
  Bruce Momjian                        |  http://candle.pha.pa.us
  pgman(at)candle(dot)pha(dot)pa(dot)us               |  (610) 359-1001
  +  If your life is a hard drive,     |  13 Roberts Road
  +  Christ can be your backup.        |  Newtown Square, Pennsylvania 19073

In response to

pgsql-admin by date

Next:From: Wojciech BernackiDate: 2002-09-29 09:59:05
Subject: Replication, High availability
Previous:From: Bruce MomjianDate: 2002-09-28 18:00:22
Subject: Re: pg_dumpall / restore issues

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group