| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Andres Freund <andres(at)anarazel(dot)de> |
| Cc: | Andrew Dunstan <andrew(at)dunslane(dot)net>, exclusion(at)gmail(dot)com, pgsql-bugs(at)lists(dot)postgresql(dot)org |
| Subject: | Re: BUG #17994: Invalidating relcache corrupts tupDesc inside ExecEvalFieldStoreDeForm() |
| Date: | 2023-07-02 21:57:03 |
| Message-ID: | 213081.1688335023@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
Andres Freund <andres(at)anarazel(dot)de> writes:
> Isn't that going to break the assumption that the key is unique within a
> transaction?
Huh? "abc" is "abc", no matter what. At least if Andrew did what
I suggested (I didn't look at the patch yet).
> Separately, will this work correctly with procedures keeping values alive
> across transactions?
That might be an issue. But couldn't we make this cache just live for
the life of the process? It's unlikely to get large.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andres Freund | 2023-07-02 22:13:20 | Re: BUG #17994: Invalidating relcache corrupts tupDesc inside ExecEvalFieldStoreDeForm() |
| Previous Message | Andres Freund | 2023-07-02 21:54:20 | Re: BUG #17994: Invalidating relcache corrupts tupDesc inside ExecEvalFieldStoreDeForm() |