Re: cache lookup failed for function 72629

This sounds like a problem I have observed, which I was able to fix by
restarting
the Slony daemon.

- Dean

2009/7/14 Lawrence Wong <lawrencew00(at)hotmail(dot)com>:
> 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.
>
> The query, I had been doing is just an update or insert into any table in
> this database.  There are about 40 tables.  Any change to the tables in the
> database results in this error.  Like I said, I had restarted the PostgreSQL
> service several times as well as restarted my Server several times to no
> avail.  I am pretty stumped and am not sure what to do short of a complete
> uninstall and reinstall of PostgreSQL.  Although I am not sure that would
> work at this point.  Probably because I'm still not sure what this error
> means.  Once again, like I said, it is just a simple update or insert into
> my tables.  I had been doing this function just a couple minutes earlier to
> this message and did not do anything out of the ordinary in the time
> between.
>
>> Date: Tue, 14 Jul 2009 09:16:05 -0400
>> Subject: Re: [GENERAL] cache lookup failed for function 72629
>> From: mmoncure(at)gmail(dot)com
>> To: lawrencew00(at)hotmail(dot)com
>> CC: pgsql-general(at)postgresql(dot)org
>>
>> On Tue, Jul 14, 2009 at 9:12 AM, Lawrence Wong<lawrencew00(at)hotmail(dot)com>
>> wrote:
>> > I'm sorry.  What does 're-applying the function source' mean?  and how
>> > would
>> > I do it?
>> >
>> > For the 'change to the table' I was talking about, I just tried to do a
>> > regular update on the table using pgAdmin III.
>> >
>> > LW . . . Lawrence
>> >
>>
>> well, the idea is to find the function that is causing the problem,
>> make a change, and save it back with pgadmin. still, this shouldn't
>> be happening, and a database restart should certainly have fixed it.
>> do we have any context for this error? do you know the query that is
>> causing it?
>>
>> merlin
>>
>> --
>> Sent via pgsql-general mailing list (pgsql-general(at)postgresql(dot)org)
>> To make changes to your subscription:
>> http://www.postgresql.org/mailpref/pgsql-general
>
> ________________________________
> We are your photos. Share us now with Windows Live Photos.