pg.ddx.io  pgsql-hackers@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Bruce Momjian <bruce@momjian.us>
To: Josh Berkus <josh@agliodbs.com>
Cc: Greg Smith <greg@2ndQuadrant.com>
Cc: Kohei KaiGai <kaigai@kaigai.gr.jp>
Cc: Dean Rasheed <dean.a.rasheed@gmail.com>
Cc: Stephen Frost <sfrost@snowman.net>
Cc: Karol Trzcionka <karlikt@gmail.com>
Cc: Mike Blackwell <mike.blackwell@rrd.com>
Cc: PgHacker <pgsql-hackers@postgresql.org>
Subject: Re: [v9.4] row level security
Date: Mon, 5 Aug 2013 08:35:45 -0400
Message-ID: <20130805123545.GA11877@momjian.us> (raw)
In-Reply-To: <51EECBB6.4010504@agliodbs.com>
References: <20130719030347.GV15510@tamriel.snowman.net>
	<51E8ADD9.5020600@2ndQuadrant.com>
	<CAEZATCXdj4E8uPHxq7jiE=1gGVB0xyeHtE8wUjHoX385sHhx4Q@mail.gmail.com>
	<CADyhKSWw1RY01tyuhRzu2HAa_+B9Z5qS6Jv+HEA1w0C9Ua2QLQ@mail.gmail.com>
	<51ED95BC.6070400@2ndQuadrant.com>
	<WM!c1afed1e22ee997691605f7faaf15e25b70edf09cbfb322a09a707e96db70172e2bd8984779fa5ae1c976322b8ceedf5!@asav-2.01.com>
	<51EEAB03.2060605@agliodbs.com>
	<51EEBA84.3030201@2ndQuadrant.com>
	<WM!bb6c4ef74149fd41bfefac93555993908116cd94a30071c92b56e85657029e20898538a11e44a85ffef2d5500c625eb0!@asav-2.01.com>
	<51EECBB6.4010504@agliodbs.com>
List-Unsubscribe: <mailto:majordomo@postgresql.org?body=unsub%20pgsql-hackers>

On Tue, Jul 23, 2013 at 11:30:14AM -0700, Josh Berkus wrote:
> Greg,
> 
> > It's more than the available experienced reviewers are willing to chew
> > on fully as volunteers.  The reward for spending review time is pretty
> > low right now.
> 
> Short of paying for review time, I don't think we have another solution
> for getting the "big patches" reviewed, except to rely on the major
> contributors who are paid full-time to hack Postgres.   You know as well
> as me that, as consultants, we can get clients to pay for 10% extra time
> for review in the course of developing a feature, but the kind of time
> which patches like Row Security, Changesets, or other "big patches" need
> nobody is going to pay for on a contract basis.  And nobody who is doing
> this in their "spare time" has that kind of block.
> 
> So I don't think there's any good solution for the "big patches".

Let me echo Josh's comments above --- in the early years, we had trouble
creating new features that required more than 1-2 weekends of
development.  We now have enough full-time developers that this is not a
problem, but now it seems features requiring more than a weekend to
_review_ are a problem, so full-time folks are again required here.

-- 
  Bruce Momjian  <bruce@momjian.us>        http://momjian.us
  EnterpriseDB                             http://enterprisedb.com

  + It's impossible for everything to be true. +


-- 
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers



view thread (165+ messages)  latest in thread

Message-ID: <20130805123545.GA11877@momjian.us>
Permalink:  ../20130805123545.GA11877@momjian.us/
Also on:    postgresql.org/message-id/20130805123545.GA11877@momjian.us

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: pgsql-hackers@postgresql.org
  Cc: bruce@momjian.us, josh@agliodbs.com, greg@2ndQuadrant.com, kaigai@kaigai.gr.jp, dean.a.rasheed@gmail.com, sfrost@snowman.net, karlikt@gmail.com, mike.blackwell@rrd.com
  Subject: Re: [v9.4] row level security
  In-Reply-To: <20130805123545.GA11877@momjian.us>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox