AFAICS, Peter's recent incomplete updating of error message wording
should have broken every last man jack of 'em. And yet there's still
some green to be seen. I think we are looking at problems in the ecpg
test scaffolding. For instance, dragonfly claims a green build, but
http://www.pgbuildfarm.org/cgi-bin/show_stage_log.pl?nm=dragonfly&dt=2007-06-04%20043001&stg=ecpg-check
shows this interesting trace:
============== running regression test queries ==============
/export/home/pgfarm/gcc/HEAD/pgsql.28740/src/interfaces/ecpg/test/./tmp_check/install//export/home/pgfarm/gcc/HEAD/inst/bin/createuser
-R -S -D -q regressuser1
/export/home/pgfarm/gcc/HEAD/pgsql.28740/src/interfaces/ecpg/test/./tmp_check/install//export/home/pgfarm/gcc/HEAD/inst/bin/createuser
-R -S -D -q connectuser
/export/home/pgfarm/gcc/HEAD/pgsql.28740/src/interfaces/ecpg/test/./tmp_check/install//export/home/pgfarm/gcc/HEAD/inst/bin/createuser
-R -S -D -q connectdb
testing connect/test1.pgc ... skipped
testing connect/test2.pgc ... ./pg_regress: bad
substitution
make[1]: Leaving directory
`/export/home/pgfarm/gcc/HEAD/pgsql.28740/src/interfaces/ecpg/test'
which says that (a) we have a scripting bug, and (b) some other layer is
failing to notice the failure. Which is two separate bugs by my count.
regards, tom lane
---------------------------(end of broadcast)---------------------------
TIP 6: explain analyze is your friend
