Re: Time to drop plpython2?

From: Mark Wong <markwkm(at)postgresql(dot)org>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Andres Freund <andres(at)anarazel(dot)de>, Peter Eisentraut <peter(dot)eisentraut(at)enterprisedb(dot)com>, pgsql-hackers(at)postgresql(dot)org, pgbf(at)twiska(dot)com, heikki(dot)linnakangas(at)iki(dot)fi
Subject: Re: Time to drop plpython2?
Date: 2022-02-23 15:58:53
Message-ID: YhZZvaoO3xPu5E2o@workstation-mark-wong
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Tue, Feb 22, 2022 at 08:50:07PM -0500, Tom Lane wrote:
> Mark Wong <markwkm(at)postgresql(dot)org> writes:
> > Take 3. :)
>
> > I've upgraded everyone to the v14 buildfarm scripts and made sure the
> > --test passed on HEAD on each one. So I hopefully didn't miss any
> > (other than the one EOL OpenSUSE version that I will plan on upgrading.)
>
> Thanks!
>
> However ... it seems like most of your animals haven't run at all
> in the last couple of days. Did you maybe forget to re-enable
> their cron jobs after messing with them, or something like that?

Uh oh, more user error. I tested run_build but run_branches wasn't
happy. I'll start working through that...

Regards,
Mark

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tomas Vondra 2022-02-23 16:07:09 Re: logical decoding and replication of sequences
Previous Message Andrew Dunstan 2022-02-23 15:54:15 Re: making pg_regress less noisy by removing boilerplate