Re: pg_upgrade should truncate/remove its logs before running

From: Julien Rouhaud <rjuju123(at)gmail(dot)com>
To: Andrew Dunstan <andrew(at)dunslane(dot)net>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Michael Paquier <michael(at)paquier(dot)xyz>, 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-07 16:31:45
Message-ID: 20220207163145.ybn472z5g65vrnc4@jrouhaud
Views: Raw Message | Whole Thread | Download mbox | Resend email
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

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Robert Haas 2022-02-07 16:36:37 Re: should vacuum's first heap pass be read-only?
Previous Message Dilip Kumar 2022-02-07 16:31:01 Re: Make relfile tombstone files conditional on WAL level