Re: installcheck failure in indirect_toast with default_toast_compression = lz4

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Michael Paquier <michael(at)paquier(dot)xyz>
Cc: Postgres hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>, Robert Haas <robertmhaas(at)gmail(dot)com>
Subject: Re: installcheck failure in indirect_toast with default_toast_compression = lz4
Date: 2021-06-05 00:28:59
Message-ID: 507591.1622852939@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Michael Paquier <michael(at)paquier(dot)xyz> writes:
> The issue is that the ordering of the tuples returned by UPDATE
> RETURNING is not completely stable. Perhaps we should just enforce
> the order of those tuples by wrapping the DMLs into a CTE and use an
> ORDER BY in the outer query.

Hmm. I'm not very clear on what that test is intending to test,
but maybe it's dependent on pglz compression, in which case the
right fix would be to force default_toast_compression = pglz
for the duration of the test.

regards, tom lane

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Jeff Davis 2021-06-05 00:34:36 Re: alter table set TABLE ACCESS METHOD
Previous Message Michael Paquier 2021-06-05 00:20:43 installcheck failure in indirect_toast with default_toast_compression = lz4