Re: Idea for reducing planning time

On Fri, 15 Dec 2000, Alfred Perlstein wrote:

> * Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> [001215 10:34] wrote:
> > >
> > > sorry, meant to respond to the original and deleted it too fast ...
> > >
> > > Tom, if the difference between 7.0 and 7.1 is such that there is a
> > > performance decrease, *please* apply the fix ... with the boon that OUTER
> > > JOINs will provide, would hate to see us with a performance hit reducing
> > > that impact ...
> > >
> > > One thing I would like to suggest for this stage of the beta, though, is
> > > that a little 'peer review' before committing the code might be something
> > > that would help 'ease' implementing stuff like this and Vadim's VACUUM
> > > code ... read through Vadim's code and see if it looks okay to you ... get
> > > Vadim to read through your code/patch and see if it looks okay to him
> > > ... it adds a day or two to the commit cycle, but at least you can say it
> > > was reviewed before committed ...
> > >
> >
> > Totally agree. In the old days, we posted all our patches to the list
> > so people could see. We used to make cvs commits only on the main
> > server, so we had the patch handy, and it made sense to post it. Now
> > that we have remote cvs, we don't do it as much, but in this case, cvs
> > diff -c is a big help.
>
> It seems that Tom has committed his fixups but we're still waiting
> on Vadim?

We can't force Vadim to commit them ... only encourage him to :)