Date: Wed, 01 Apr 1998 09:22:51 -0800 (PST) From: Simon Shapiro <shimon@simon-shapiro.org> To: (Andrew McNaughton) <andrew@squiz.co.nz> Cc: freebsd-database@FreeBSD.ORG Subject: Re: Mailing list search interface Message-ID: <XFMail.980401092251.shimon@simon-shapiro.org> In-Reply-To: <v02120d00b147ee0ebbcd@[192.168.1.1]>
next in thread | previous in thread | raw e-mail | index | archive | help
On 01-Apr-98 Andrew McNaughton wrote: > As I say, so far I'm using mysql. It seems the discussion here has been > about postgreSQL with references to oracle. Can someone give me or point > me to a comparison between postgreSQL and mysql. Print the docs for both, take a day off and read :-) Build both, install both, and run both. > Is the emphasis on postgreSQL due to licensing differences or functional > ones? For me, it is only one of the issues. The others are that Posgres is a much easier candidate for enhancements towards High Availability Server. > A quick look over the postgresSQL suggests that it has several query > language features that mysql lacks (eg sub queries), and the docs place > more emphasis on extension. It appears it does not do multithreading. Very true. Postgres is very extendable, both in the upper layer (new types, indices, methods, rules, etc.), the logic layer (completeness of the relational model and SQL compliance). It does not do multithreading, but it does multi-processing. Each database connection is a process. A front-end (application) can maintain multiple database connection. Since the interaction between database access threads is via shared memory, this is not a problem. The lack of threads (probably historical) forced the definition of an indpendant lock manager, and independant and modular storage manager. This allows people like myself to easily deveop different locking and storage facilities, which, again, allow me to contemplate clustered, multi-host access. > How do they compare on speed? Postgres used to be slow, but I gather > that postgreSQL is better. If your funtionality can be served by mysql, you probably should use it. It is smaller, simpler, and thus probably faster. If you need the functionality or Features that Postgres offers, then sheer speed is not the only consideration. I suspect most of the speed issue will be resolved with the new lovk manager I wrote, and the new storage manager I am writing. Simon To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-database" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?XFMail.980401092251.shimon>