Re: installcheck failure in indirect_toast with default_toast_compression = lz4 - Mailing list pgsql-hackers

From Tom Lane
Subject Re: installcheck failure in indirect_toast with default_toast_compression = lz4
Date
Msg-id 507591.1622852939@sss.pgh.pa.us
Whole thread Raw
In response to installcheck failure in indirect_toast with default_toast_compression = lz4  (Michael Paquier <michael@paquier.xyz>)
Responses Re: installcheck failure in indirect_toast with default_toast_compression = lz4
List pgsql-hackers
Michael Paquier <michael@paquier.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



pgsql-hackers by date:

Previous
From: Michael Paquier
Date:
Subject: installcheck failure in indirect_toast with default_toast_compression = lz4
Next
From: Jeff Davis
Date:
Subject: Re: alter table set TABLE ACCESS METHOD