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-08 09:27:11
Message-ID: 4519d7da-7402-cff3-d577-0bc8511e0c9a@enterprisedb.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

On 02.09.21 10:15, Peter Eisentraut wrote:
> On 31.08.21 22:43, Tom Lane wrote:
>> I find variant 1 a bit cleaner, and safer.  I'd rather default to
>> assuming that RECORD doesn't hash, when we don't have enough info
>> to be sure.
>
> Ok, here is a more polished patch for that.

committed

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message PG Bug reporting form 2021-09-08 13:11:49 BUG #17185: PostgreSQL performance GNU vs LLVM
Previous Message Julien Rouhaud 2021-09-08 07:26:59 Re: BUG #17183: missing websearch_to_tsquery