Re: BUG #17994: Invalidating relcache corrupts tupDesc inside ExecEvalFieldStoreDeForm() - Mailing list pgsql-bugs

From Andrew Dunstan
Subject Re: BUG #17994: Invalidating relcache corrupts tupDesc inside ExecEvalFieldStoreDeForm()
Date
Msg-id d3c6db0a-4231-d9af-ee5c-206e8067331c@dunslane.net
Whole thread Raw
In response to Re: BUG #17994: Invalidating relcache corrupts tupDesc inside ExecEvalFieldStoreDeForm()  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-bugs


On 2023-08-21 Mo 12:30, Tom Lane wrote:
Andrew Dunstan <andrew@dunslane.net> writes:
On 2023-08-21 Mo 08:33, Alvaro Herrera wrote:
Hmm ... when exactly do these values get freed if no longer needed?  Is
the theory that leaking them is not relevant?
Not sure I understand "relevant" here. They don't get freed. There will 
be at most one entry per row in pg_attribute where atthasmissing is 
true.
Yeah.  My feeling is that as long as we don't make duplicate hashtable
entries, there will never be so many entries that it'd be worth the
cost and intellectual complexity of trying to clean them up.  When
and if that theory is disproven, we can think harder; but for now
I think this approach is good enough.
			


Fix pushed to all relevant branches.


cheers


andrew

--
Andrew Dunstan
EDB: https://www.enterprisedb.com

pgsql-bugs by date:

Previous
From: PG Bug reporting form
Date:
Subject: BUG #18067: Droping function that was used to generate column drops the column, even after `DROP EXPRESSION`
Next
From: Jeff Davis
Date:
Subject: Re: pg_dump assertion failure with "-n pg_catalog"