pgsql: Rename a function to avoid naming conflict in parallel regressio - Mailing list pgsql-committers

From Tom Lane
Subject pgsql: Rename a function to avoid naming conflict in parallel regressio
Date
Msg-id E1UvUES-0006JF-JH@gemulon.postgresql.org
Whole thread Raw
List pgsql-committers
Rename a function to avoid naming conflict in parallel regression tests.

Commit 31a891857a128828d47d93c63e041f3b69cbab70 added some tests in
plpgsql.sql that used a function rather unthinkingly named "foo()".
However, rangefuncs.sql has some much older tests that create a function
of that name, and since these test scripts run in parallel, there is a
chance of failures if the timing is just right.  Use another name to
avoid that.  Per buildfarm (failure seen today on "hamerkop", but
probably it's happened before and not been noticed).

Branch
------
REL9_3_STABLE

Details
-------
http://git.postgresql.org/pg/commitdiff/e407192c937d993be1a4f5636a1afa57cf492f6f

Modified Files
--------------
src/test/regress/expected/plpgsql.out |   72 ++++++++++++++++-----------------
src/test/regress/sql/plpgsql.sql      |   56 ++++++++++++-------------
2 files changed, 64 insertions(+), 64 deletions(-)


pgsql-committers by date:

Previous
From: Tom Lane
Date:
Subject: pgsql: Rename a function to avoid naming conflict in parallel regressio
Next
From: Michael Meskes
Date:
Subject: pgsql: Also escape double quotes for ECPG's #line statement.