Re: Running a Simple Update Statement Fails, Second Time Suceeds.

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: "Kumar, Virendra" <Virendra(dot)Kumar(at)guycarp(dot)com>
Cc: Adrian Klaver <adrian(dot)klaver(at)aklaver(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-04 15:17:18
Message-ID: 3000.1567610238@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

"Kumar, Virendra" <Virendra(dot)Kumar(at)guycarp(dot)com> writes:
> Here is function code:

Hm, nothing very exciting in there. But the known reasons for this
type of error involve something changing a table rowtype that the
function uses (that is, ALTER TABLE ADD COLUMN or the like). Or
dropping/recreating such a table altogether. Is there any part
of your workflow that redefines the type of
product_owner.external_sys_class_code_pres.audit_update_dt or
product_owner.external_sys_class_code_pres ?

Also, you still didn't tell us the server's version.

regards, tom lane

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Luca Ferrari 2019-09-04 16:16:00 Re: PG11.2 - wal_level =minimal max_wal_senders = 0
Previous Message Jason Ralph 2019-09-04 15:15:19 PG11.2 - wal_level =minimal max_wal_senders = 0