From: Tom Lane <tgl@sss.pgh.pa.us>
To: Jehan-Guillaume de Rorthais <jgdr@dalibo.com>
Cc: pgsql-bugs@lists.postgresql.org
Subject: Re: [BUG] plpgsql RETURN QUERY with toasted fields -vs- DROP/TRUNCATE
Date: Sat, 29 Aug 2020 13:47:19 -0400
Message-ID: <3568911.1598723239@sss.pgh.pa.us> (raw)
In-Reply-To: <20200828174342.2ac34e27@firost>
References: <20200828174342.2ac34e27@firost>
Jehan-Guillaume de Rorthais <jgdr@dalibo.com> writes:
> We discovered a bug in plpgsql.
> When using RETURN QUERY on a relation with some toasted values and when this
> relaiton is later dropped or truncated, an error is raised at the end of the
> function.
This isn't particularly RETURN QUERY's fault; there are any number of ways
to produce the same sort of error. I reproduced it with
declare r record;
...
for r in SELECT str FROM temp_rel loop
return next r.str;
end loop;
as well as
declare r record;
...
SELECT str INTO r FROM temp_rel LIMIT 1;
DROP TABLE temp_rel;
--TRUNCATE TABLE temp_rel;
return r.str;
I guess we could forcibly detoast values in enough places to close all the
gaps, but the performance costs might be annoying. I think a case can
definitely be made for saying "don't do that".
(Another idea, perhaps, might be to detoast only in volatile functions,
reasoning that a nonvolatile one can't drop the table.)
regards, tom lane
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, jgdr@dalibo.com, pgsql-bugs@lists.postgresql.org
Subject: Re: [BUG] plpgsql RETURN QUERY with toasted fields -vs- DROP/TRUNCATE
In-Reply-To: <3568911.1598723239@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