| 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-02 08:15:37 |
| Message-ID: | 7fb17b3d-13dc-fc28-17ce-9c302d676bd8@enterprisedb.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
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.
| Attachment | Content-Type | Size |
|---|---|---|
| v2-0001-Disable-anonymous-record-hash-support-except-in-s.patch | text/plain | 14.9 KB |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | PG Bug reporting form | 2021-09-02 10:54:03 | BUG #17176: Error raised on valid query |
| Previous Message | Alexander Lakhin | 2021-09-02 04:00:01 | Re: BUG #17126: Server crashes on dropping user while enumerating owned objects that are droppped concurrently |