Re: Calling PLpgSQL function with composite type fails with an error: "ERROR: could not open relation with OID ..."

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Ashutosh Sharma <ashu(dot)coek88(at)gmail(dot)com>
Cc: pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Calling PLpgSQL function with composite type fails with an error: "ERROR: could not open relation with OID ..."
Date: 2019-12-27 03:50:34
Message-ID: 21313.1577418634@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Ashutosh Sharma <ashu(dot)coek88(at)gmail(dot)com> writes:
> Okay. Thanks for that fix. You've basically forced
> revalidate_rectypeid() to update the PLpgSQL_rec's rectypeid
> irrespective of typcache entry requires re-validation or not.

Right. The assignment is cheap enough that it hardly seems
worth avoiding.

regards, tom lane

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Justin Pryzby 2019-12-27 03:51:57 Re: ALTER INDEX fails on partitioned index
Previous Message yuzuko 2019-12-27 03:37:15 Re: Autovacuum on partitioned table