pg.ddx.io  pgsql-bugs@postgresql.org mailing list archive  

help / color / mirror / Atom feed
From: Peter Eisentraut <peter.eisentraut@enterprisedb.com>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: David Rowley <dgrowleyml@gmail.com>
Cc: sait.nisanci@microsoft.com, PostgreSQL mailing lists <pgsql-bugs@lists.postgresql.org>
Subject: Re: BUG #17158: Distinct ROW fails with Postgres 14
Date: Wed, 8 Sep 2021 11:27:11 +0200
Message-ID: <4519d7da-7402-cff3-d577-0bc8511e0c9a@enterprisedb.com> (raw)
In-Reply-To: <7fb17b3d-13dc-fc28-17ce-9c302d676bd8@enterprisedb.com>
References: <17158-8a2ba823982537a4@postgresql.org>
	<CAApHDvp0w_5YY=7pxPkymtv7Oc0cGS=+jtiBvXrfcM6gLjT5Pg@mail.gmail.com>
	<bc0ec85a-68cf-1b99-e80c-ee0c55b936db@enterprisedb.com>
	<496046.1629843371@sss.pgh.pa.us>
	<c182f5c8-fdf3-80a0-fa43-4ed7e87d4d47@enterprisedb.com>
	<2021952.1630442634@sss.pgh.pa.us>
	<7fb17b3d-13dc-fc28-17ce-9c302d676bd8@enterprisedb.com>

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





view thread (14+ messages)  latest in thread

Message-ID: <4519d7da-7402-cff3-d577-0bc8511e0c9a@enterprisedb.com>
Permalink:  ../4519d7da-7402-cff3-d577-0bc8511e0c9a@enterprisedb.com/
Also on:    postgresql.org/message-id/4519d7da-7402-cff3-d577-0bc8511e0c9a@enterprisedb.com

 · 

reply
Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: pgsql-bugs@postgresql.org
  Cc: peter.eisentraut@enterprisedb.com, tgl@sss.pgh.pa.us, dgrowleyml@gmail.com, pgsql-bugs@lists.postgresql.org
  Subject: Re: BUG #17158: Distinct ROW fails with Postgres 14
  In-Reply-To: <4519d7da-7402-cff3-d577-0bc8511e0c9a@enterprisedb.com>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox