pg.ddx.io  pgsql-bugs@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Tom Lane <tgl@sss.pgh.pa.us>
To: zeroimpl@gmail.com
Cc: pgsql-bugs@lists.postgresql.org
Subject: Re: BUG #15913: Could not open relation with oid on PL/pgSQL method referencing temporary table that got recreated
Date: Thu, 15 Aug 2019 15:23:31 -0400
Message-ID: <23768.1565897011@sss.pgh.pa.us> (raw)
In-Reply-To: <15913-a7e112e16dedcffc@postgresql.org>
References: <15913-a7e112e16dedcffc@postgresql.org>

PG Bug reporting form <noreply@postgresql.org> writes:
> I have some SQL which works fine in 9.x and 10.x, but fails in 11.x and 12.x
> (I tested on various Docker images).
> One of the functions declares a variable whose type matches a temporary
> table. If I drop and recreate that temporary table twice in the same
> session, I get an error like: "ERROR:  could not open relation with OID
> xxx". This occurs on the second call to the DoSomething() function after the
> temporary table has been recreated. 

I've pushed a fix for this -

https://git.postgresql.org/gitweb/?p=postgresql.git;a=commitdiff;h=6070ccdd179f34efecc92d6679a141093...

Thanks for the report!

			regards, tom lane





view thread (2+ messages)

Message-ID: <23768.1565897011@sss.pgh.pa.us>
Permalink:  ../23768.1565897011@sss.pgh.pa.us/
Also on:    postgresql.org/message-id/23768.1565897011@sss.pgh.pa.us

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: pgsql-bugs@postgresql.org
  Cc: tgl@sss.pgh.pa.us, zeroimpl@gmail.com, pgsql-bugs@lists.postgresql.org
  Subject: Re: BUG #15913: Could not open relation with oid on PL/pgSQL method referencing temporary table that got recreated
  In-Reply-To: <23768.1565897011@sss.pgh.pa.us>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox