From: | Andrew Dunstan <andrew(at)dunslane(dot)net> |
---|---|
To: | Alexander Lakhin <exclusion(at)gmail(dot)com> |
Cc: | pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: The xversion-upgrade test fails to stop server |
Date: | 2024-06-02 18:39:02 |
Message-ID: | 9dcff844-8ca7-42c2-bd6d-0183d194aaeb@dunslane.net |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On 2024-05-30 Th 11:00, Alexander Lakhin wrote:
> Hello Andrew,
>
> While reviewing recent buildfarm failures, I came across this one:
> https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=crake&dt=2024-05-23%2004%3A11%3A03
>
>
> upgrade.crake/REL_16_STABLE/REL9_5_STABLE-ctl4.log
> waiting for server to shut
> down...........................................................................................................................
> failed
> pg_ctl: server does not shut down
>
> Looking at:
> https://github.com/PGBuildFarm/client-code/blob/05014d50e/PGBuild/Modules/TestUpgradeXversion.pm#L641
>
>
> I see that ctl4.log is created after updating extensions and
> REL9_5_STABLE-update_extensions.log contains:
> You are now connected to database "contrib_regression_redis_fdw" as
> user "buildfarm".
> ALTER EXTENSION "hstore" UPDATE;
> ALTER EXTENSION
> You are now connected to database "contrib_regression_btree_gin" as
> user "buildfarm".
> ALTER EXTENSION "btree_gin" UPDATE;
> ALTER EXTENSION
> ...
> but I see no corresponding server log file containing these commands
> in the
> failure log.
>
> When running the same test locally, I find these in inst/upgrade_log.
>
> Maybe uploading this log file too would help to understand what is the
> cause of the failure...
>
>
Yeah, I'll fix that.
cheers
andrew
--
Andrew Dunstan
EDB: https://www.enterprisedb.com
From | Date | Subject | |
---|---|---|---|
Next Message | Neil Conway | 2024-06-02 19:17:21 | Optimizing COPY with SIMD |
Previous Message | Alexander Korotkov | 2024-06-02 13:18:11 | Re: POC: GROUP BY optimization |