aboutsummaryrefslogtreecommitdiff
path: root/src/backend/utils/adt/numutils.c
diff options
context:
space:
mode:
authorMichael Paquier <michael@paquier.xyz>2022-12-27 14:35:56 +0900
committerMichael Paquier <michael@paquier.xyz>2022-12-27 14:35:56 +0900
commit9814ff550046f825b751803191b29a2fbbc79283 (patch)
tree0fc2143a3fdc70d135c920ceeedd94be1229dab4 /src/backend/utils/adt/numutils.c
parent2259c661dc4ecd88ac22b5358248f47ca5a5d4fc (diff)
downloadpostgresql-9814ff550046f825b751803191b29a2fbbc79283.tar.gz
postgresql-9814ff550046f825b751803191b29a2fbbc79283.zip
Add custom filtering rules to the TAP tests of pg_upgrade
002_pg_upgrade.pl gains support for a new environment variable called "filter_rules", that can be used to point to a file that includes a set of custom regular expressions that would be applied to the dumps of the origin and target clusters when doing a cross-version test (aka when defining olddump and oldinstall), to give the possibility to reshape dynamically the dumps in the same way as the internals of the buildfarm code so as the tests are able to pass in scenarios where one expects them to even if pg_dump generates slightly-different outputs depending on the versions involved. This option is not used when pg_upgrade runs with the same version for the origin and target clusters, and it is the last piece I see as required to be able to plug-in more efficiently the TAP tests of pg_upgrade with the buildfarm or just a CI. Author: Anton A. Melnikov Discussion: https://postgr.es/m/49f389ba-95ce-8a9b-09ae-f60650c0e7c7@inbox.ru
Diffstat (limited to 'src/backend/utils/adt/numutils.c')
0 files changed, 0 insertions, 0 deletions