X-Original-To: pgsql-advocacy-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [200.46.204.2]) by svr1.postgresql.org (Postfix) with ESMTP id BE32DD1C4ED; Tue, 27 Apr 2004 17:51:29 -0300 (ADT) Received: from svr1.postgresql.org ([200.46.204.71]) by localhost (neptune.hub.org [200.46.204.2]) (amavisd-new, port 10024) with ESMTP id 25482-01; Tue, 27 Apr 2004 17:51:26 -0300 (ADT) Received: from noon.pghoster.com (noon.pghoster.com [64.246.0.64]) by svr1.postgresql.org (Postfix) with ESMTP id 4F60BD1BA62; Tue, 27 Apr 2004 17:51:24 -0300 (ADT) Received: from [66.119.208.134] (helo=travelamericas.com) by noon.pghoster.com with asmtp (Exim 4.24) id 1BIZY2-00046g-3I; Tue, 27 Apr 2004 15:51:22 -0500 Message-ID: <408EBBA9.70709@travelamericas.com> Date: Tue, 27 Apr 2004 12:59:37 -0700 From: Chris Travers User-Agent: Mozilla/5.0 (X11; U; Linux i586; en-US; rv:1.6) Gecko/20040113 X-Accept-Language: en-us, en MIME-Version: 1.0 To: "Jim C. Nasby" Cc: PostgreSQL-development , PostgreSQL advocacy Subject: Re: [HACKERS] What can we learn from MySQL? References: <200404230409.i3N49jC02890@candle.pha.pa.us> <4088B944.1050007@familyhealth.com.au> <20040423192730.GO41429@nasby.net> In-Reply-To: <20040423192730.GO41429@nasby.net> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-AntiAbuse: This header was added to track abuse, please include it with any abuse report X-AntiAbuse: Primary Hostname - noon.pghoster.com X-AntiAbuse: Original Domain - postgresql.org X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12] X-AntiAbuse: Sender Address Domain - travelamericas.com X-Virus-Scanned: by amavisd-new at postgresql.org X-Spam-Status: No, hits=0.2 tagged_above=0.0 required=5.0 tests=RCVD_IN_RFCI, RCVD_IN_SORBS X-Spam-Level: X-Archive-Number: 200404/269 X-Sequence-Number: 4241 Jim C. Nasby wrote: >Maybe also a more generic section about how PGSQL is different from >other databases. Maybe I'm just dense, but it took me a long time to >figure out the whole lack of stored procedures thing (yes, PGSQL >obviously has the functionality, but many experienced DBAs won't >associate functions with stored procs). Pointing out the documentation >on MVCC and how it changes how you want to use the database would be >good, as would links to documentation on what postgresql.conf settings >you want to change out of the box. > > > I think this is a good idea. And you seem to be suggesting that it includes information on differences in nomenclature as well. >On the other topics... >I think the biggest service PGSQL could provide to the open source >community is a resource that teaches people with no database experience >the fundamentals of databases. If people had an understanding of what a >RDBMS should be capable of and how it should be used, they wouldn't pick >MySQL. > > I think that this is incredibly important. Many many developers choose MySQL because MySQL really does make the effort in this regard. This strategy has helped both MySQL and Red Hat become the commercial successes they are today. >Having a windows port is critical for 'student mindshare'. If PGSQL can't >play on windows, professors can't use it. Likewise, installation on OS X >should be made as easy as possible. > > PostgreSQL *can* play on Windows (via Cygwin) and I am not sure that this is so important to student mindshare. Howener, it is important for another reason: a windows port (even one labled "for development use only") would go a LONG way towards recruiting new faces into our community, as it would lower the barrier to entry for using the database (yes, the Cygwin installer because of the ipc stuff is a reasonable barrier to entry). Best Wishes, Chris Travers Metatron Technology Consulting