Re: Strange assertion using VACOPT_FREEZE in vacuum.c - Mailing list pgsql-hackers

From Stephen Frost
Subject Re: Strange assertion using VACOPT_FREEZE in vacuum.c
Date
Msg-id 20150317173157.GJ29780@tamriel.snowman.net
Whole thread Raw
In response to Re: Strange assertion using VACOPT_FREEZE in vacuum.c  (Alvaro Herrera <alvherre@2ndquadrant.com>)
Responses Re: Strange assertion using VACOPT_FREEZE in vacuum.c  (Magnus Hagander <magnus@hagander.net>)
List pgsql-hackers
* Alvaro Herrera (alvherre@2ndquadrant.com) wrote:
> I went to change this patch status in the commitfest app, and the app
> told me I cannot change the status in the current commitfest.  Please
> somebody with commitfest mace superpowers set it as ready for committer.

I'm afraid the issue is a business decision which is incorrect as it's
complaining that it's in a "Closed" state and you're trying to change it
to an "Open" state.  While it's neat to think a patch could never be
reopened, it's clearly not accurate.

Adding Magnus to this, as I'm pretty sure he has some code to go hack
(or perhaps just remove.. :).
Thanks!
    Stephen

pgsql-hackers by date:

Previous
From: Alvaro Herrera
Date:
Subject: Re: Strange assertion using VACOPT_FREEZE in vacuum.c
Next
From: Bruce Momjian
Date:
Subject: Re: Rethinking the parameter access hooks for plpgsql's benefit