Re: BUG #17212: pg_amcheck fails on checking temporary relations

Andrew Dunstan <andrew@dunslane.net>

From: Andrew Dunstan <andrew@dunslane.net>
To: Tom Lane <tgl@sss.pgh.pa.us>, Peter Geoghegan <pg@bowt.ie>
Cc: Mark Dilger <mark.dilger@enterprisedb.com>, Robert Haas <robertmhaas@gmail.com>, Pavel Borisov <pashkin.elfe@gmail.com>, Alexander Lakhin <exclusion@gmail.com>, PostgreSQL-development <pgsql-hackers@postgresql.org>
Date: 2021-10-14T20:50:51Z
Lists: pgsql-bugs, pgsql-hackers
On 10/14/21 12:15 AM, Tom Lane wrote:
> Peter Geoghegan <pg@bowt.ie> writes:
>> Any idea what the problems on drongo are?
>> https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=drongo&dt=2021-10-14%2001%3A27%3A19
> It says
>
> # pg_ctl start failed; logfile:
> 2021-10-14 02:10:33.996 UTC [491848:1] LOG:  starting PostgreSQL 14.0, compiled by Visual C++ build 1923, 64-bit
> 2021-10-14 02:10:33.999 UTC [491848:2] LOG:  could not bind IPv4 address "127.0.0.1": Only one usage of each socket address (protocol/network address/port) is normally permitted.
> 2021-10-14 02:10:33.999 UTC [491848:3] HINT:  Is another postmaster already running on port 54407? If not, wait a few seconds and retry.
> 2021-10-14 02:10:33.999 UTC [491848:4] WARNING:  could not create listen socket for "127.0.0.1"
> 2021-10-14 02:10:33.999 UTC [491848:5] FATAL:  could not create any TCP/IP sockets
> 2021-10-14 02:10:34.000 UTC [491848:6] LOG:  database system is shut down
> Bail out!  pg_ctl start failed
>
> Looks like a transient/phase of the moon issue to me.
>
> 			



Bowerbird is having similar issues, so I don't think this is just a
transient.


cheers


andrew

--
Andrew Dunstan
EDB: https://www.enterprisedb.com




Commits

  1. Remove unstable pg_amcheck tests.

  2. pg_amcheck: avoid unhelpful verification attempts.

  3. amcheck: Skip unlogged relations in Hot Standby.

  4. amcheck: Skip unlogged relations during recovery.