Christoph Berg <myon@debian.org> writes:
> (Fwiw, I can't see your error message in
> https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=sidewinder&dt=2020-01-07%2022%3A45%3A24)
sidewinder is currently broken due to an unrelated problem.
The case Amit is worried about is only manifesting on the
back branches, eg here:
https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=sidewinder&dt=2020-01-02%2018%3A45%3A25
where we're getting postmaster start failures like this one:
2020-01-02 19:51:05.685 CET [24138:1] LOG: starting PostgreSQL 12.1 on x86_64-unknown-netbsd7.0, compiled by gcc (nb2
20150115)4.8.4, 64-bit
2020-01-02 19:51:05.686 CET [24138:2] LOG: listening on Unix socket "/tmp/sxAcn7SAzt/.s.PGSQL.56110"
2020-01-02 19:51:05.687 CET [24138:3] FATAL: insufficient file descriptors available to start server process
2020-01-02 19:51:05.687 CET [24138:4] DETAIL: System allows 19, we need at least 20.
2020-01-02 19:51:05.687 CET [24138:5] LOG: database system is shut down
This would happen if anything is causing the postmaster to have
a few more open files than the test added by commit
d207038053837ae9365df2776371632387f6f655 is allowing for. It's
a test bug and nothing more.
Why sidewinder is not showing this in HEAD too is an interesting
question, but it isn't. However, it could be that on another
platform (ie bionic) the problem does manifest in HEAD.
regards, tom lane
