pg.ddx.io  pgsql-students@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Joshua D. Drake <jd@commandprompt.com>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: Andrew Dunstan <andrew@dunslane.net>
Cc: pgsql-hackers@postgresql.org
Subject: Re: Seeking Google SoC Mentors
Date: Mon, 26 Feb 2007 18:25:51 -0800
Message-ID: <45E396AF.40005@commandprompt.com> (raw)
In-Reply-To: <9533.1172542238@sss.pgh.pa.us>
References: <200702261311.39684.josh@agliodbs.com>
	<45E34F9F.7090002@dunslane.net>
	<200702261550.14414.wt@penguintechs.org>
	<45E36722.1080703@dunslane.net>
	<9533.1172542238@sss.pgh.pa.us>

Tom Lane wrote:
> Andrew Dunstan <andrew@dunslane.net> writes:
>> Well, here's a question. Given the recent discussion re full 
>> disjunction, I'd like to know what sort of commitment we are going to 
>> give people who work on proposed projects.
> 
> Um, if you mean are we going to promise to accept a patch in advance of
> seeing it, the answer is certainly not.  Still, a SoC author can improve
> his chances in all the usual ways, primarily by getting discussion and
> rough consensus on a spec and then on an implementation sketch before
> he starts to do much code.  Lots of showstopper problems can be caught
> at that stage.

Tom,

Correct me if I am wrong, but would the way that HOT has been handled be
a good way for the SoC people to do things?

Joshua D. Drake


> 
> I think the main problems with the FD patch were (1) much of the
> community was never actually sold on it being a useful feature,
> and (2) the implementation was not something anyone wanted to accept
> into core, because of its klugy API.  Both of these points could have
> been dealt with before a line of code had been written, but they were
> not :-(
> 
> 			regards, tom lane
> 
> ---------------------------(end of broadcast)---------------------------
> TIP 6: explain analyze is your friend
> 


-- 

      === The PostgreSQL Company: Command Prompt, Inc. ===
Sales/Support: +1.503.667.4564 || 24x7/Emergency: +1.800.492.2240
Providing the most comprehensive  PostgreSQL solutions since 1997
             http://www.commandprompt.com/

Donate to the PostgreSQL Project: http://www.postgresql.org/about/donate
PostgreSQL Replication: http://www.commandprompt.com/products/




view thread (26+ messages)  latest in thread

Message-ID: <45E396AF.40005@commandprompt.com>
Permalink:  ../45E396AF.40005@commandprompt.com/
Also on:    postgresql.org/message-id/45E396AF.40005@commandprompt.com

 · 

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 from your mail client; the link fills in
  the headers below: reply via email
  Some clients, webmail especially, drop In-Reply-To and References from
  a link, and the reply then starts a new thread: use the mbox below.

  To: pgsql-students@postgresql.org
  Cc: jd@commandprompt.com, tgl@sss.pgh.pa.us, andrew@dunslane.net, pgsql-hackers@postgresql.org
  Subject: Re: Seeking Google SoC Mentors
  In-Reply-To: <45E396AF.40005@commandprompt.com>
  References: <200702261311.39684.josh@agliodbs.com> <45E34F9F.7090002@dunslane.net> <200702261550.14414.wt@penguintechs.org> <45E36722.1080703@dunslane.net> <9533.1172542238@sss.pgh.pa.us> <45E396AF.40005@commandprompt.com>

* 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