Re: Keep elog(ERROR) and ereport(ERROR) calls in the cold path

From: David Rowley <dgrowleyml(at)gmail(dot)com>
To: Michael Paquier <michael(at)paquier(dot)xyz>
Cc: Andres Freund <andres(at)anarazel(dot)de>, PostgreSQL Developers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: Keep elog(ERROR) and ereport(ERROR) calls in the cold path
Date: 2020-08-03 09:05:52
Message-ID: CAApHDvqWaQvzUPrPMZ7vYcVwzRFP+zbQwhdQ630xgUVBj0O2Wg@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Mon, 3 Aug 2020 at 19:54, Michael Paquier <michael(at)paquier(dot)xyz> wrote:
> Worth noting that the patch set fails to apply. I have moved this
> entry to the next CF, waiting on author.

Thanks.

NB: It's not a patch set. It's 3 different versions of the patch.
They're not all meant to apply at once. Probably the CF bot wasn't
aware of that though :-(

David

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Kyotaro Horiguchi 2020-08-03 09:17:56 Re: Is it worth accepting multiple CRLs?
Previous Message Ashutosh Sharma 2020-08-03 09:05:38 Re: recovering from "found xmin ... from before relfrozenxid ..."