I'm not exactly sure what was wrong. But I tried making a change on another database on the same server and it was ok. So I thought deleting the problem database and restoring it again would do the trick and it did. So problem solved I guess. Although I'm still not sure what happened . . .
LW . . . Lawrence
From: lawrencew00@hotmail.com
To: tgl@sss.pgh.pa.us
CC: mmoncure@gmail.com; pgsql-general@postgresql.org
Subject: RE: [GENERAL] cache lookup failed for function 72629
Date: Tue, 14 Jul 2009 14:33:19 +0000
.ExternalClass .EC_hmmessage P
{padding:0px;}
.ExternalClass body.EC_hmmessage
{font-size:10pt;font-family:Verdana;}
I guess I'll ask on the slony-i mailing list also. thanks for your hlep.
LW . . . Lawrence
> To: lawrencew00@hotmail.com
> CC: mmoncure@gmail.com; pgsql-general@postgresql.org
> Subject: Re: [GENERAL] cache lookup failed for function 72629
> Date: Tue, 14 Jul 2009 10:18:10 -0400
> From: tgl@sss.pgh.pa.us
>
> Lawrence Wong <lawrencew00@hotmail.com> writes:
> > I had been using Slony-I together with another database on a server on a different machine. I had been testing my replication constantly dropping and creating my Slony-I tables. This is not out of the ordinary though. I had been doing this for many days now.
>
> Hmm, try asking about it on the Slony mailing lists. Slony is known to
> cause strange errors if you do something it's not expecting. I suspect
> that the missing function is actually a Slony trigger function, in which
> case you could probably clean up by dropping the trigger --- but get
> some help first, or you may mess up Slony even further.
>
> regards, tom lane
Internet Explorer 8 makes surfing easier. Get it now!
Attention all humans. We are your photos. Free us.
