Re: post-freeze damage control

From: Peter Eisentraut <peter(at)eisentraut(dot)org>
To: Michael Paquier <michael(at)paquier(dot)xyz>, Thomas Munro <thomas(dot)munro(at)gmail(dot)com>
Cc: Robert Haas <robertmhaas(at)gmail(dot)com>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: post-freeze damage control
Date: 2024-04-09 05:59:08
Message-ID: 38e4f7ef-cf8d-4721-ad9a-1e0be0bb0f4f@eisentraut.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 09.04.24 00:58, Michael Paquier wrote:
> That's more linked to the fact that I was going silent without a
> laptop for a few weeks before the end of the release cycle, and a way
> to say to not count on me, while I was trying to keep my room clean to
> avoid noise for others who would rush patches. It is a vacation
> period for schools in Japan as the fiscal year finishes at the end of
> March, while the rest of the world still studies/works, so that makes
> trips much easier with areas being less busy when going abroad. If
> you want to limit commit activity during this period, the answer is
> simple then: require that all the committers live in Japan.

Well, due to the Easter holiday being earlier this year, I adopted a
similar approach: Go on vacation the last week of March and watch the
rest from the pool. :) So far I feel this was better for my well-being.

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Michael Paquier 2024-04-09 06:00:27 Re: NLS doesn't work for pg_combinebackup
Previous Message Tom Lane 2024-04-09 05:55:39 Re: post-freeze damage control