| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Andres Freund <andres(at)anarazel(dot)de> |
| Cc: | Sait Talha Nisanci <Sait(dot)Nisanci(at)microsoft(dot)com>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>, Metin Doslu <Metin(dot)Doslu(at)microsoft(dot)com> |
| Subject: | Re: Crash in record_type_typmod_compare |
| Date: | 2021-03-31 19:34:22 |
| Message-ID: | 3297888.1617219262@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Andres Freund <andres(at)anarazel(dot)de> writes:
> On 2021-03-31 13:10:50 -0400, Tom Lane wrote:
>> Couldn't we just
>> teach record_type_typmod_compare to say "not equal" if it sees a
>> null tupdesc?
> Won't that lead to an accumulation of dead hash table entries over time?
Yeah, if you have repeat failures there, which doesn't seem very likely.
Still, I take your point that we're doing it the first way in other
places, so maybe inventing a different way here isn't good.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Mark Dilger | 2021-03-31 19:34:41 | Re: multi-install PostgresNode fails with older postgres versions |
| Previous Message | Joel Jacobson | 2021-03-31 19:32:09 | Re: Idea: Avoid JOINs by using path expressions to follow FKs |