Re: Getting a move on for 8.2 beta

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Bruce Momjian <bruce(at)momjian(dot)us>
Cc: Robert Treat <xzilla(at)users(dot)sourceforge(dot)net>, pgsql-hackers(at)postgresql(dot)org, David Fetter <david(at)fetter(dot)org>, Peter Eisentraut <peter_e(at)gmx(dot)net>, "Joshua D(dot) Drake" <jd(at)commandprompt(dot)com>, josh(at)agliodbs(dot)com
Subject: Re: Getting a move on for 8.2 beta
Date: 2006-09-03 03:46:45
Message-ID: 8566.1157255205@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Bruce Momjian <bruce(at)momjian(dot)us> writes:
> ... The GUC comment/default patch had tons of
> emails, but no other committers got involved to review or commit the
> patch. Peter, who knows GUC well, looked at it, but said he didn't
> review it enough.

Peter has made it pretty clear that he didn't care for the
refactorization aspect of that patch.

> I just spent 1/2 hour fixing the multi-value UPDATE
> patch for the code drift caused by UPDATE/RETURNING. The patch is a
> simple grammar macro. Any coder could have taken that, reviewed it, and
> applied it, but no one did.

Perhaps that's because nobody but you wanted it to go in.

Some amount of the issue here is that people won't work on patches they
don't approve of; that's certainly the case for me. I have more than
enough to do working on patches I do think should go in, and I get tired
of having to repeatedly object to the same bad patch. Do you remember
Sturgeon's Law? It applies to patches too.

regards, tom lane

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2006-09-03 03:49:37 Re: problem with volatile functions in subselects ?
Previous Message Joshua D. Drake 2006-09-03 03:39:39 Re: gBorg status?