pg.ddx.io  pgsql-committers@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Jeff Davis <pgsql@j-davis.com>
To: Andrew Dunstan <andrew@dunslane.net>
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, 09 Mar 2023 14:21:20 -0800
Message-ID: <3db075bb0327c0ebbca130692eb47dc1376c4766.camel@j-davis.com> (raw)
In-Reply-To: <a317cbc32c6d94f73e4e22c5c64745c0f8b7846f.camel@j-davis.com>
References: <E1paJJm-002i7N-Dh@gemulon.postgresql.org>
	<0a364430-266e-1e1a-d5d8-1a5273c9ddb6@dunslane.net>
	<a317cbc32c6d94f73e4e22c5c64745c0f8b7846f.camel@j-davis.com>

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 tried locally testing the upgrades, but it seems like the version of
master before my change (8dff2f224f) also fails the pg_upgrade test for
all versions earlier than 10. I assume there are some extra steps to
make the test work for earlier versions, but I haven't looked deeply
yet.

Regards,
	Jeff Davis






view thread (5+ messages)  latest in thread

Message-ID: <3db075bb0327c0ebbca130692eb47dc1376c4766.camel@j-davis.com>
Permalink:  ../3db075bb0327c0ebbca130692eb47dc1376c4766.camel@j-davis.com/
Also on:    postgresql.org/message-id/3db075bb0327c0ebbca130692eb47dc1376c4766.camel@j-davis.com

 · 

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: pgsql@j-davis.com, andrew@dunslane.net, jdavis@postgresql.org
  Subject: Re: pgsql: pg_upgrade: copy locale and encoding information to new cluster.
  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>

* 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