| From: | Greg Stark <stark(at)mit(dot)edu> |
|---|---|
| To: | Robert Haas <robertmhaas(at)gmail(dot)com> |
| Cc: | PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>, "Joshua D(dot) Drake" <jd(at)commandprompt(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Andres Freund <andres(at)2ndquadrant(dot)com> |
| Subject: | Re: Rethinking the parameter access hooks for plpgsql's benefit |
| Date: | 2015-03-09 17:33:23 |
| Message-ID: | CAM-w4HNcc-xc4cekWOy9rGO_jbtddWBD43mxgCJ0Aq3wziyFDQ@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
I don't think Tom, or that matter anyone needs to forgo working on changes
at any time. The only effect missing a commitfest deadline means is that
other reviewers don't offer any promises to give any feedback on it before
this round of the commitfest is done.
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.
There has been the suggestion that commiters should concentrate on reviews
rather than fresh development during commitfests but nobody is going to do
100% reviewing work for the whole time and nobody could seriously suggest
Tom hasn't pulled his weight reviewing patches.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Jeff Janes | 2015-03-09 17:36:07 | Re: Turning off HOT/Cleanup sometimes |
| Previous Message | Alvaro Herrera | 2015-03-09 17:28:32 | Re: Question about lazy_space_alloc() / linux over-commit |