Re: pg_upgrade should truncate/remove its logs before running

From: Julien Rouhaud <rjuju123(at)gmail(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Michael Paquier <michael(at)paquier(dot)xyz>, Andrew Dunstan <andrew(at)dunslane(dot)net>, Justin Pryzby <pryzby(at)telsasoft(dot)com>, Peter Eisentraut <peter(dot)eisentraut(at)enterprisedb(dot)com>, Daniel Gustafsson <daniel(at)yesql(dot)se>, Bruce Momjian <bruce(at)momjian(dot)us>, pgsql-hackers(at)lists(dot)postgresql(dot)org
Subject: Re: pg_upgrade should truncate/remove its logs before running
Date: 2022-02-06 07:03:11
Message-ID: 20220206070311.yxg2xuoie4gxfsyp@jrouhaud
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Sun, Feb 06, 2022 at 01:58:21AM -0500, Tom Lane wrote:
> Michael Paquier <michael(at)paquier(dot)xyz> writes:
> > So, it took me some time to get back to this thread, and looked at it
> > for the last couple of days... The buildfarm client v14 has been
> > released on the 29th of January, which means that we are good to go.
>
> As already mentioned, there's been no notice to buildfarm owners ...
> so has Andrew actually made a release?

There's a v14 release on the github project ([1]) from 8 days ago, so it seems
so.

[1] https://github.com/PGBuildFarm/client-code/releases/tag/REL_14

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Michael Paquier 2022-02-06 07:04:54 Re: pg_upgrade should truncate/remove its logs before running
Previous Message Michael Paquier 2022-02-06 07:00:58 Re: Ensure that STDERR is empty during connect_ok