| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | "Bossart, Nathan" <bossartn(at)amazon(dot)com> |
| Cc: | "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: pg_upgrade test chatter |
| Date: | 2021-10-19 18:00:40 |
| Message-ID: | 1903398.1634666440@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
"Bossart, Nathan" <bossartn(at)amazon(dot)com> writes:
> I run 'make check-world' a lot, and I typically use parallelism and
> redirect stdout to /dev/null as suggested in the docs [0]. This seems
> to eliminate all of the test chatter except for this one message:
> NOTICE: database "regression" does not exist, skipping
Yeah, that's bugged me too ever since we got to the point where that
was the only output ...
> We could also just create the
> database it is trying to drop to silence the NOTICE.
... but that seems like a mighty expensive way to fix it.
createdb is pretty slow on older/slower buildfarm animals.
Maybe we could run the stderr output through "grep -v", or the like?
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Alvaro Herrera | 2021-10-19 18:07:17 | Re: Parallel vacuum workers prevent the oldest xmin from advancing |
| Previous Message | Bossart, Nathan | 2021-10-19 17:41:29 | pg_upgrade test chatter |