Re: BUG #17158: Distinct ROW fails with Postgres 14

From: Peter Eisentraut <peter(dot)eisentraut(at)enterprisedb(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: David Rowley <dgrowleyml(at)gmail(dot)com>, sait(dot)nisanci(at)microsoft(dot)com, PostgreSQL mailing lists <pgsql-bugs(at)lists(dot)postgresql(dot)org>
Subject: Re: BUG #17158: Distinct ROW fails with Postgres 14
Date: 2021-09-14 14:39:39
Message-ID: 2f0f926d-23c9-2ded-4032-dee85be733dc@enterprisedb.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

On 10.09.21 21:27, Tom Lane wrote:
> Perhaps it'd work to put the phony entry into fcinfo->flinfo->fn_mcxt
> instead of CacheMemoryContext.
>
> BTW, skink's failure can be reproduced pretty quickly by running the
> attached under valgrind.

Ok, the attached patch fixes the valgrind error.

Attachment Content-Type Size
0001-Fix-hash_array.patch text/plain 1.3 KB

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Tom Lane 2021-09-14 15:02:13 Re: BUG #17158: Distinct ROW fails with Postgres 14
Previous Message PG Bug reporting form 2021-09-14 13:44:11 BUG #17193: Issue with pg_output login