Skip site navigation (1) Skip section navigation (2)

Re: Patch queue concern

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Bruce Momjian <bruce(at)momjian(dot)us>
Cc: Simon Riggs <simon(at)2ndquadrant(dot)com>, "Joshua D(dot) Drake" <jd(at)commandprompt(dot)com>, Gregory Stark <stark(at)enterprisedb(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Patch queue concern
Date: 2007-03-29 18:14:21
Message-ID: 26221.1175192061@sss.pgh.pa.us (view raw or flat)
Thread:
Lists: pgsql-hackers
Bruce Momjian <bruce(at)momjian(dot)us> writes:
> The basic problem is we have a lot of complex patches coming in, and
> many from people who do not have years of experience with submitting
> patches to PostgreSQL.  A complex patch from a novice user takes a lot
> of time to review, and frankly, we don't have enough experienced
> developers doing such reviews.

Part of the issue is that we have a lot of new developers who are trying
to solve hard problems without having learned their way around the code
by fixing easy stuff.  It was easier some years ago for people to learn
that way, because there was way more low-hanging fruit back then.  But
there's still some out there.  I have a distinct sense that we are
getting patches from people who are trying to run before they've learned
to walk.

			regards, tom lane

In response to

pgsql-hackers by date

Next:From: Merlin MoncureDate: 2007-03-29 18:18:03
Subject: Re: Fixing insecure security definer functions
Previous:From: Bruce MomjianDate: 2007-03-29 18:12:39
Subject: Re: tsearch_core patch for inclusion

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group