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

Re: PostgreSQL committer history?

From: "Joshua D(dot) Drake" <jd(at)commandprompt(dot)com>
To: Ron Mayer <rm_pg(at)cheapcomplexdevices(dot)com>
Cc: pgsql-advocacy(at)postgresql(dot)org
Subject: Re: PostgreSQL committer history?
Date: 2006-03-09 19:42:06
Message-ID: 4410850E.1070404@commandprompt.com (view raw or flat)
Thread:
Lists: pgsql-advocacy
>
> Correct me if I'm wrong, but I would expect the mechanics
> of committing to be
>   1. typing "cvs diff" to see what changed, and
>   1b. reading *extremely* carefully
>   2. typing "cvs commit" with the same explanation.
>
> If committing is really easier than submitting patches,
> it seems someone should either make committing harder or
> make submitting patches easier.
The difference is anyone can send a patch. Only a handful can commit.

Joshua D. Drae


>
> ---------------------------(end of broadcast)---------------------------
> TIP 9: In versions below 8.0, the planner will ignore your desire to
>       choose an index scan if your joining column's datatypes do not
>       match
>


-- 
The PostgreSQL Company - Command Prompt, Inc. 1.503.667.4564
PostgreSQL Replication, Consulting, Custom Development, 24x7 support
Managed Services, Shared and Dedicated Hosting
Co-Authors: PLphp, PLperl - http://www.commandprompt.com/


In response to

pgsql-advocacy by date

Next:From: Ron MayerDate: 2006-03-09 19:51:07
Subject: Re: PostgreSQL committer history?
Previous:From: Ron MayerDate: 2006-03-09 19:37:56
Subject: Re: PostgreSQL committer history?

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