aboutsummaryrefslogtreecommitdiff
path: root/src/backend/utils/adt/array_typanalyze.c
diff options
context:
space:
mode:
authorPeter Eisentraut <peter_e@gmx.net>2012-09-16 22:26:33 -0400
committerPeter Eisentraut <peter_e@gmx.net>2012-09-16 22:26:33 -0400
commitb2e3bea3afe9618764a8f15cc7d6d95036b7638b (patch)
tree63f010b733bfa090de5bd6b96c5a43d511958761 /src/backend/utils/adt/array_typanalyze.c
parent3b8968f25232ad09001bf35ab4cc59f5a501193e (diff)
downloadpostgresql-b2e3bea3afe9618764a8f15cc7d6d95036b7638b.tar.gz
postgresql-b2e3bea3afe9618764a8f15cc7d6d95036b7638b.zip
PL/Python: Improve Python 3 regression test setup
Currently, we are making mangled copies of plpython/{expected,sql} to plpython/python3/{expected,sql}, and run the tests in plpython/python3. This has the disadvantage that the regression.diffs file, if any, ends up in plpython/python3, which is not the normal location. If we instead make the mangled copies in plpython/{expected,sql}/python3/, we can run the tests from the normal directory, regression.diffs ends up the normal place, and the pg_regress invocation also becomes a lot simpler. It's also more obvious at run time what's going on, because the tests end up being named "python3/something" in the test output.
Diffstat (limited to 'src/backend/utils/adt/array_typanalyze.c')
0 files changed, 0 insertions, 0 deletions