Horton

Re: pg_upgrade should truncate/remove its logs before running

Julien Rouhaud <rjuju123@gmail.com>

View thread View on postgr.es
From: Julien Rouhaud <rjuju123@gmail.com>
To: Andrew Dunstan <andrew@dunslane.net>
Cc: Tom Lane <tgl@sss.pgh.pa.us>, Michael Paquier <michael@paquier.xyz>, Justin Pryzby <pryzby@telsasoft.com>, Peter Eisentraut <peter.eisentraut@enterprisedb.com>, Daniel Gustafsson <daniel@yesql.se>, Bruce Momjian <bruce@momjian.us>, pgsql-hackers@lists.postgresql.org
Date: 2022-02-07T16:31:45Z
Lists: pgsql-hackers 
On Mon, Feb 07, 2022 at 11:00:22AM -0500, Andrew Dunstan wrote:
> 
> On 2/6/22 19:39, Tom Lane wrote:
> >
> > I note, though, that there's still not been any email to the buildfarm
> > owners list about this update.
> 
> The announcement was held up in list moderation for 20 hours or so.

I've certainly experienced way more than that in the past.  Are volunteers
needed?

Commits

  1. pg_upgrade: Move all the files generated internally to a subdirectory