Re: Statement-level rollback

From: Michael Paquier <michael(at)paquier(dot)xyz>
To: Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>
Cc: Andres Freund <andres(at)anarazel(dot)de>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Robert Haas <robertmhaas(at)gmail(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>, "Tsunakawa, Takayuki" <tsunakawa(dot)takay(at)jp(dot)fujitsu(dot)com>
Subject: Re: Statement-level rollback
Date: 2019-02-13 01:12:03
Views: Raw Message | Whole Thread | Download mbox | Resend email
Lists: pgsql-hackers

On Tue, Feb 12, 2019 at 07:13:45PM -0300, Alvaro Herrera wrote:
> It was reasonable to close this patch as returned-with-feedback in
> January commitfest, but what you did here was first move it to the March
> commitfest and then close it as returned-with-feedback in the March
> commitfest, which has not even started. That makes no sense.

Except if the CF app does not leave any place for error, particularly
as it is not possible to move back a patch to a previous commit fest
once it has been moved to the next one. In this case, it looks that I
did a mistake in moving the patch first, my apologies for that. There
were many patches to classify last week, so it may be possible that I
did similar mistakes for some other patches.

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Michael Paquier 2019-02-13 01:25:46 Re: Reaping Temp tables to avoid XID wraparound
Previous Message Thomas Munro 2019-02-13 00:52:45 Re: dsa_allocate() faliure