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

From: Ashutosh Sharma <ashu(dot)coek88(at)gmail(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
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 11:15:18
Message-ID: CAE9k0Pn-8QtJ3TR+aEFVPaekUvrMx=nR3=DKZEHy2AFaRGyMyg@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Fri, Dec 27, 2019 at 9:20 AM Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
>
> 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.
>

Agreed.

--
With Regards,
Ashutosh Sharma
EnterpriseDB:http://www.enterprisedb.com

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Alvaro Herrera 2019-12-27 13:08:28 Re: Libpq support to connect to standby server as priority
Previous Message Fabien COELHO 2019-12-27 10:58:18 Re: doc: vacuum full, fillfactor, and "extra space"