From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com> |
Cc: | "Kumar, Virendra" <Virendra(dot)Kumar(at)guycarp(dot)com>, "pgsql-general(at)lists(dot)postgresql(dot)org" <pgsql-general(at)lists(dot)postgresql(dot)org> |
Subject: | Re: Running a Simple Update Statement Fails, Second Time Suceeds. |
Date: | 2019-09-03 21:41:12 |
Message-ID: | 7112.1567546872@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com> writes:
> On 9/3/19 1:56 PM, Kumar, Virendra wrote:
>> Here is simple query, I am running via function call. This statement
>> runs fine as SQL but when put in function as plpgsql it failes with
>> error below, when I ran second times in same session it succeeds:
> We will need to see the function definition.
Also, what PG version is that? This looks a bit like bug #15913,
but it might be something else.
>> This message is intended only for the use of the addressee and may contain
>> information that is PRIVILEGED AND CONFIDENTIAL.
>>
>> If you are not the intended recipient, you are hereby notified that any
>> dissemination of this communication is strictly prohibited. If you have
>> received this communication in error, please erase all copies of the message
>> and its attachments and notify the sender immediately. Thank you.
I rather wonder whether I'm even allowed to read this, let alone
answer it. You do realize that this sort of add-on is completely
silly on a public mailing list?
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Kumar, Virendra | 2019-09-03 22:08:48 | Re: Running a Simple Update Statement Fails, Second Time Suceeds. |
Previous Message | Adrian Klaver | 2019-09-03 21:32:09 | Re: Running a Simple Update Statement Fails, Second Time Suceeds. |