Commit
a4327296d taught pg_regress proper to do this, but
missed the opportunity to do likewise in the isolationtester
and ecpg variants of pg_regress. Seems like this might be
helpful for tracking down issues exposed by those tests.
expectfile_source[MAXPGPATH];
char cmd[MAXPGPATH * 3];
char *testname_dash;
+ char *appnameenv;
snprintf(inprg, sizeof(inprg), "%s/%s", inputdir, testname);
outfile_stdout,
outfile_stderr);
+ appnameenv = psprintf("PGAPPNAME=ecpg/%s", testname_dash);
+ putenv(appnameenv);
+
pid = spawn_process(cmd);
if (pid == INVALID_PID)
exit(2);
}
+ unsetenv("PGAPPNAME");
+ free(appnameenv);
+
+ free(testname_dash);
free(outfile_stdout);
free(outfile_stderr);
free(outfile_source);
char expectfile[MAXPGPATH];
char psql_cmd[MAXPGPATH * 3];
size_t offset = 0;
+ char *appnameenv;
/* need to do the path lookup here, check isolation_init() for details */
if (!looked_up_isolation_exec)
exit(2);
}
+ appnameenv = psprintf("PGAPPNAME=isolation/%s", testname);
+ putenv(appnameenv);
+
pid = spawn_process(psql_cmd);
if (pid == INVALID_PID)
exit(2);
}
+ unsetenv("PGAPPNAME");
+ free(appnameenv);
+
return pid;
}
static void
initialize_environment(void)
{
+ /*
+ * Set default application_name. (The test_function may choose to
+ * override this, but if it doesn't, we have something useful in place.)
+ */
putenv("PGAPPNAME=pg_regress");
if (nolocale)