Re: Rethinking the parameter access hooks for plpgsql's benefit - Mailing list pgsql-hackers

From Greg Stark
Subject Re: Rethinking the parameter access hooks for plpgsql's benefit
Date
Msg-id CAM-w4HNcc-xc4cekWOy9rGO_jbtddWBD43mxgCJ0Aq3wziyFDQ@mail.gmail.com
Whole thread Raw
In response to Re: Rethinking the parameter access hooks for plpgsql's benefit  (Robert Haas <robertmhaas@gmail.com>)
List pgsql-hackers
<p dir="ltr">I don't think Tom, or  that matter anyone needs to forgo working on changes at any time. The only effect
missinga commitfest deadline means is that other reviewers don't offer any promises to give any feedback on it before
thisround of the commitfest is done.<p dir="ltr">We don't have a policy of requiring code reviews before changes are
committed-- it's up to the commuters judgement whether the patch is type for committing.<p dir="ltr">There has been the
suggestionthat commiters should concentrate on reviews rather than fresh development during commitfests but nobody is
goingto do 100% reviewing work for the whole time and nobody could seriously suggest Tom hasn't pulled his weight
reviewingpatches.<br /> 

pgsql-hackers by date:

Previous
From: Alvaro Herrera
Date:
Subject: Re: Question about lazy_space_alloc() / linux over-commit
Next
From: Jeff Janes
Date:
Subject: Re: Turning off HOT/Cleanup sometimes