Re: Concurrent modification of plpgsql function body

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Alvaro Herrera <alvherre(at)commandprompt(dot)com>
Cc: Alex Vinogradovs <AVinogradovs(at)Clearpathnet(dot)com>, pgsql-general <pgsql-general(at)postgresql(dot)org>
Subject: Re: Concurrent modification of plpgsql function body
Date: 2008-01-07 19:22:37
Message-ID: 23770.1199733757@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

Alvaro Herrera <alvherre(at)commandprompt(dot)com> writes:
> Alex Vinogradovs wrote:
>> I mean I re-create the function with the same signature but
>> different body, and when the application invokes that function
>> again, it starts getting those errors.

> Are you using CREATE OR REPLACE FUNCTION, or DROP FUNCTION followed by
> CREATE FUNCTION?

Perhaps more to the point, we need to see a complete example. I don't
see how either way of changing a plpgsql function would result in the
described error.

regards, tom lane

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Greg Smith 2008-01-07 19:27:40 Re: calculating shared data memory space
Previous Message Alex Vinogradovs 2008-01-07 19:19:30 Re: Concurrent modification of plpgsql function body