pg.ddx.io  pgsql-committers@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Andrew Dunstan <andrew@dunslane.net>
To: Jeff Davis <pgsql@j-davis.com>
To: Jeff Davis <jdavis@postgresql.org>
To: pgsql-committers@lists.postgresql.org
Subject: Re: pgsql: pg_upgrade: copy locale and encoding information to new cluster.
Date: Thu, 9 Mar 2023 17:30:29 -0500
Message-ID: <ec25ebcc-1e22-52be-50ab-98bee4eb462e@dunslane.net> (raw)
In-Reply-To: <3db075bb0327c0ebbca130692eb47dc1376c4766.camel@j-davis.com>
References: <E1paJJm-002i7N-Dh@gemulon.postgresql.org>
	<0a364430-266e-1e1a-d5d8-1a5273c9ddb6@dunslane.net>
	<a317cbc32c6d94f73e4e22c5c64745c0f8b7846f.camel@j-davis.com>
	<3db075bb0327c0ebbca130692eb47dc1376c4766.camel@j-davis.com>


On 2023-03-09 Th 17:21, Jeff Davis wrote:
> On Thu, 2023-03-09 at 09:35 -0800, Jeff Davis wrote:
>> On Thu, 2023-03-09 at 12:21 -0500, Andrew Dunstan wrote:
>>> This looks like it broke cross version upgrade testing. Old
>>> versions
>>> don't have datlocprovider.
>> Thank you, fixing. Just waiting for some CI tests.
> I fixed most of the problems, but I'm still seeing a failure on crake:
>
> https://buildfarm.postgresql.org/cgi-bin/show_stage_log.pl?nm=crake&dt=2023-03-09%2019%3A37%3A04...
>
> It seems only the 94 upgrade is failing, and the message seems
> unrelated to my change:
>
> "could not load library "$libdir/uuid-ossp": ERROR:  could not access
> file "$libdir/uuid-ossp": No such file or directory
> In database: contrib_regression_uuid-ossp"
>
> Is that a transient failure?


I think it's a different issue, probably related to the fact that crake 
is taking meson for a walk.


cheers


andrew

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

view thread (5+ messages)

Message-ID: <ec25ebcc-1e22-52be-50ab-98bee4eb462e@dunslane.net>
Permalink:  ../ec25ebcc-1e22-52be-50ab-98bee4eb462e@dunslane.net/
Also on:    postgresql.org/message-id/ec25ebcc-1e22-52be-50ab-98bee4eb462e@dunslane.net

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients from your mail client; the link fills in
  the headers below: reply via email
  Some clients, webmail especially, drop In-Reply-To and References from
  a link, and the reply then starts a new thread: use the mbox below.

  To: pgsql-committers@postgresql.org
  Cc: andrew@dunslane.net, pgsql@j-davis.com, jdavis@postgresql.org
  Subject: Re: pgsql: pg_upgrade: copy locale and encoding information to new cluster.
  In-Reply-To: <ec25ebcc-1e22-52be-50ab-98bee4eb462e@dunslane.net>
  References: <E1paJJm-002i7N-Dh@gemulon.postgresql.org> <0a364430-266e-1e1a-d5d8-1a5273c9ddb6@dunslane.net> <a317cbc32c6d94f73e4e22c5c64745c0f8b7846f.camel@j-davis.com> <3db075bb0327c0ebbca130692eb47dc1376c4766.camel@j-davis.com> <ec25ebcc-1e22-52be-50ab-98bee4eb462e@dunslane.net>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox