Re: pgstattuple: add test for coverage - Mailing list pgsql-hackers

From Dong Wook Lee
Subject Re: pgstattuple: add test for coverage
Date
Msg-id CAAcByaJAH4mCRin2oewz6hr=g4yb+K_eELM5tu++o2_mhsfBkQ@mail.gmail.com
Whole thread Raw
In response to Re: pgstattuple: add test for coverage  (Andres Freund <andres@anarazel.de>)
Responses Re: pgstattuple: add test for coverage  (Andres Freund <andres@anarazel.de>)
List pgsql-hackers
> Which indeed is the case, e.g. on 32bit systems it fails:
>
> https://cirrus-ci.com/task/4619535222308864?logs=test_world_32#L253
>
>
https://api.cirrus-ci.com/v1/artifact/task/4619535222308864/testrun/build-32/testrun/pgstattuple/regress/regression.diffs
>
>   table_len | tuple_count | tuple_len | tuple_percent | dead_tuple_count | dead_tuple_len | dead_tuple_percent |
free_space| free_percent
 
>
-----------+-------------+-----------+---------------+------------------+----------------+--------------------+------------+--------------
> -   1171456 |        5000 |    560000 |          47.8 |             5000 |         560000 |               47.8 |
7452 |         0.64
 
> +   1138688 |        5000 |    540000 |         47.42 |             5000 |         540000 |              47.42 |
14796|          1.3
 
>  (1 row)
>
> ...
>
>
> You definitely can't rely on such details not to change across platforms.


Thank you for letting me know I'll fix it and check if there's any problem.



pgsql-hackers by date:

Previous
From: Andres Freund
Date:
Subject: Re: [Proposal] Add foreign-server health checks infrastructure
Next
From: Andres Freund
Date:
Subject: Re: pg_upgrade test failure