Skip site navigation (1) Skip section navigation (2)

pgsql: Avoid function name conflict when plpgsql and rangefuncs

From: tgl(at)svr1(dot)postgresql(dot)org (Tom Lane)
To: pgsql-committers(at)postgresql(dot)org
Subject: pgsql: Avoid function name conflict when plpgsql and rangefuncs
Date: 2005-07-01 20:29:03
Message-ID: 20050701202903.8DE8352A55@svr1.postgresql.org (view raw or flat)
Thread:
Lists: pgsql-committers
Log Message:
-----------
Avoid function name conflict when plpgsql and rangefuncs regression tests
execute in parallel.  Spotted by Peter.

Modified Files:
--------------
    pgsql/src/test/regress/sql:
        plpgsql.sql (r1.31 -> r1.32)
        (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/test/regress/sql/plpgsql.sql.diff?r1=1.31&r2=1.32)
    pgsql/src/test/regress/expected:
        plpgsql.out (r1.36 -> r1.37)
        (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/test/regress/expected/plpgsql.out.diff?r1=1.36&r2=1.37)

pgsql-committers by date

Next:From: Tom LaneDate: 2005-07-01 20:37:53
Subject: Re: pgsql: Clarify code to double \\ and '.
Previous:From: Tom LaneDate: 2005-07-01 19:40:57
Subject: Re: pgsql: Update for roles: < * Allow limits on per-db/user connections >

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group