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 5C235D1B50F; Tue, 27 Apr 2004 12:59:03 -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 56127-01; Tue, 27 Apr 2004 12:59:01 -0300 (ADT) Received: from ganymede.hub.org (u46n208.hfx.eastlink.ca [24.222.46.208]) by svr1.postgresql.org (Postfix) with ESMTP id 711B3D1B4E0; Tue, 27 Apr 2004 12:59:00 -0300 (ADT) Received: by ganymede.hub.org (Postfix, from userid 1000) id DAE2D37E7D; Tue, 27 Apr 2004 12:58:59 -0300 (ADT) Received: from localhost (localhost [127.0.0.1]) by ganymede.hub.org (Postfix) with ESMTP id D767D37E2F; Tue, 27 Apr 2004 12:58:59 -0300 (ADT) Date: Tue, 27 Apr 2004 12:58:59 -0300 (ADT) From: "Marc G. Fournier" X-X-Sender: scrappy@ganymede.hub.org To: Tim Conrad Cc: PostgreSQL-development , PostgreSQL advocacy Subject: Re: [HACKERS] What can we learn from MySQL? In-Reply-To: <20040427152753.GA34713@external.timconrad.org> Message-ID: <20040427124336.R60328@ganymede.hub.org> References: <200404262213.44601.jm@poure.com> <200404262041.i3QKfZs28845@candle.pha.pa.us> <20040427152753.GA34713@external.timconrad.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Virus-Scanned: by amavisd-new at postgresql.org X-Spam-Status: No, hits=0.0 tagged_above=0.0 required=5.0 tests= X-Spam-Level: X-Archive-Number: 200404/251 X-Sequence-Number: 4223 On Tue, 27 Apr 2004, Tim Conrad wrote: > 2) There doesn't seem to be a clear roadmap on Postgres features. > When certian things are expected. There's the TODO list that > Bruce maintains, but it only outlines 'near' fixes. MySQL has a > nice listing of what to expect in certian future versions. Not possible for us, since we have no "upper management" that dictates what features get added, for when ... > I know > it's not a perfect list, but it'd be nice to know when full blown > replication will be included in PostgreSQL as an example. Never, since there is no such thing as a 'full blown replication', since there is no *one* way to do replication ... > 3) There's the issues of 'advanced database features' in general. > Many MySQL applications perform much of their logic in the > application level, instead of the database level. They do this > because there aren't things like triggers or stored procedures > in MySQL. As the saying goes, 'if mohammad won't go to the > mountain, bring the mountian to mohammad'. Why not do some > simple explainations as to why these things are good, and what > they do, and how to use them in real context? Just a matter of someone writing and submitting it ... how are your writing skills? :) > 4) As other peole have noted, there's no windows build readily > available for Postgres. There may be, but it's difficult to > find. If someone's used to running, say, Oracle, and all they > have is a windows machine to test something out on, MySQL has > compiled binaries ready to go. there is no native windows currently available, but its being worked on for 7.5 ... after which, a pre-compiled binary becomes automatic ... ---- Marc G. Fournier Hub.Org Networking Services (http://www.hub.org) Email: scrappy@hub.org Yahoo!: yscrappy ICQ: 7615664