Re: pg_upgrade should truncate/remove its logs before running

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Michael Paquier <michael(at)paquier(dot)xyz>
Cc: 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 06:58:21
Message-ID: 668240.1644130701@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

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?

regards, tom lane

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Michael Paquier 2022-02-06 07:00:58 Re: Ensure that STDERR is empty during connect_ok
Previous Message Fabien COELHO 2022-02-06 06:58:06 Re: libpq async duplicate error results