pg.ddx.io pgsql-sql@postgresql.org mailing list archivehelp / color / mirror / Atom feed
commentds on redhats new database 4+ messages / 3 participants [nested] [flat]
* commentds on redhats new database @ 2001-06-20 22:28 clayton cottingham <drfrog@smartt.com> 2001-06-20 23:13 ` Re: commentds on redhats new database Ross J. Reedstrom <reedstrm@rice.edu> 0 siblings, 1 reply; 4+ messages in thread From: clayton cottingham @ 2001-06-20 22:28 UTC (permalink / raw) To: pgsql-sql hello: i thought id find out what people think about this: http://www.zdnet.com/zdnn/stories/news/0,4586,2778706,00.html?chkpt=zdnn_rt_latest which basically points out that redhat will be making their own database based off of postgres7.1 my main concern is that this could cause some sort of splintering of the code base could this potentially happen? what other concerns could there be? ^ permalink raw reply [nested|flat] 4+ messages in thread
* Re: commentds on redhats new database 2001-06-20 22:28 commentds on redhats new database clayton cottingham <drfrog@smartt.com> @ 2001-06-20 23:13 ` Ross J. Reedstrom <reedstrm@rice.edu> 2001-06-21 05:32 ` Re: commentds on redhats new database Tom Lane <tgl@sss.pgh.pa.us> 0 siblings, 1 reply; 4+ messages in thread From: Ross J. Reedstrom @ 2001-06-20 23:13 UTC (permalink / raw) To: pgsql-sql On Wed, Jun 20, 2001 at 03:28:34PM -0700, clayton cottingham wrote: > hello: > > i thought id find out what people think about this: > http://www.zdnet.com/zdnn/stories/news/0,4586,2778706,00.html?chkpt=zdnn_rt_latest > > which basically points out that redhat will be making their own database > based off of postgres7.1 Quoting: The Red Hat Database, as it is likely to be called, is based on PostgreSQL 7.1. Included in the package will be Red Hat Installer, which will aid users in quickly installing the database, robust transaction support and advanced locking capabilities. It will comply with SQL92, ODBC and JDBC APIs. > > my main concern is that this could cause some sort of splintering of the > code base I'll be interesting to see how their offering differs from GreatBridge. And if their going to claim SQL'92 compliance, have they done all the SCHEMA support work? ;-) > > could this potentially happen? Sure, we're BSD, so they're under no obligation to share any code changes with us. Haven't noticed many new @redhat.com email address over on HACKERS, though, so I wonder if they've done much work on the core. > > what other concerns could there be? > Getting bug reports from code we can't look at. Ross ^ permalink raw reply [nested|flat] 4+ messages in thread
* Re: commentds on redhats new database 2001-06-20 22:28 commentds on redhats new database clayton cottingham <drfrog@smartt.com> 2001-06-20 23:13 ` Re: commentds on redhats new database Ross J. Reedstrom <reedstrm@rice.edu> @ 2001-06-21 05:32 ` Tom Lane <tgl@sss.pgh.pa.us> 2001-06-21 05:45 ` Re: commentds on redhats new database Ross J. Reedstrom <reedstrm@rice.edu> 0 siblings, 1 reply; 4+ messages in thread From: Tom Lane @ 2001-06-21 05:32 UTC (permalink / raw) To: Ross J. Reedstrom <reedstrm@rice.edu>; +Cc: pgsql-sql "Ross J. Reedstrom" <reedstrm@rice.edu> writes: >> could [a fork] potentially happen? > Sure, we're BSD, so they're under no obligation to share any code changes > with us. I really doubt that RedHat is silly enough to want to fork the code. They haven't forked Linux, gcc, gdb, etc, but have been upstanding contributors to all those projects; why would they do it differently with Postgres? > Haven't noticed many new @redhat.com email address over on HACKERS, > though, so I wonder if they've done much work on the core. Some folk at RedHat's Toronto offices are gearing up to contribute work; I was up there to talk with them just a couple weeks ago. They've not been real visible yet though ... (hey Patrick et al: if you're reading this, it's past time to introduce yourselves). regards, tom lane ^ permalink raw reply [nested|flat] 4+ messages in thread
* Re: commentds on redhats new database 2001-06-20 22:28 commentds on redhats new database clayton cottingham <drfrog@smartt.com> 2001-06-20 23:13 ` Re: commentds on redhats new database Ross J. Reedstrom <reedstrm@rice.edu> 2001-06-21 05:32 ` Re: commentds on redhats new database Tom Lane <tgl@sss.pgh.pa.us> @ 2001-06-21 05:45 ` Ross J. Reedstrom <reedstrm@rice.edu> 0 siblings, 0 replies; 4+ messages in thread From: Ross J. Reedstrom @ 2001-06-21 05:45 UTC (permalink / raw) To: Tom Lane <tgl@sss.pgh.pa.us>; +Cc: pgsql-sql On Thu, Jun 21, 2001 at 01:32:10AM -0400, Tom Lane wrote: > "Ross J. Reedstrom" <reedstrm@rice.edu> writes: > >> could [a fork] potentially happen? > > > Sure, we're BSD, so they're under no obligation to share any code changes > > with us. > > I really doubt that RedHat is silly enough to want to fork the code. > They haven't forked Linux, gcc, gdb, etc, but have been upstanding > contributors to all those projects; why would they do it differently > with Postgres? Hey, he did say _potentially_. I agree that it's not at all _likely_. > > > Haven't noticed many new @redhat.com email address over on HACKERS, > > though, so I wonder if they've done much work on the core. > > Some folk at RedHat's Toronto offices are gearing up to contribute work; > I was up there to talk with them just a couple weeks ago. They've not > been real visible yet though ... (hey Patrick et al: if you're reading > this, it's past time to introduce yourselves). Sounds cool. The more the merrier, I say. Ross ^ permalink raw reply [nested|flat] 4+ messages in thread
end of thread, other threads:[~2001-06-21 05:45 UTC | newest] Thread overview: 4+ messages (download: mbox mbox.gz follow: Atom feed) -- links below jump to the message on this page -- 2001-06-20 22:28 commentds on redhats new database clayton cottingham <drfrog@smartt.com> 2001-06-20 23:13 ` Ross J. Reedstrom <reedstrm@rice.edu> 2001-06-21 05:32 ` Tom Lane <tgl@sss.pgh.pa.us> 2001-06-21 05:45 ` Ross J. Reedstrom <reedstrm@rice.edu>
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