Re: Question: test "aggregates" failed in 32-bit machine

From: "Jonathan S(dot) Katz" <jkatz(at)postgresql(dot)org>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Tomas Vondra <tomas(dot)vondra(at)enterprisedb(dot)com>
Cc: "kuroda(dot)hayato(at)fujitsu(dot)com" <kuroda(dot)hayato(at)fujitsu(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>, John Naylor <john(dot)naylor(at)enterprisedb(dot)com>, Michael Paquier <michael(at)paquier(dot)xyz>
Subject: Re: Question: test "aggregates" failed in 32-bit machine
Date: 2022-10-01 20:58:28
Message-ID: 72f2bcf5-e173-e1d0-5606-2a43d2d3c9ca@postgresql.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 10/1/22 3:13 PM, Tom Lane wrote:

> I'm still of the opinion that we need to revert this code for now.

[RMT hat, but speaking just for me] reading through Tom's analysis, this
seems to be the safest path forward. I have a few questions to better
understand:

1. How invasive would the revert be?
2. Are the other user-visible items that would be impacted?
3. Is there an option of disabling the feature by default viable?

Thanks,

Jonathan

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Andres Freund 2022-10-01 22:15:14 Re: longfin and tamandua aren't too happy but I'm not sure why
Previous Message Andres Freund 2022-10-01 20:38:21 Re: interrupted tap tests leave postgres instances around