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

Re: Decide between Postgresql and Mysql (help of

From: PFC <lists(at)peufeu(dot)com>
To: "Scott Marlowe" <smarlowe(at)g2switchworks(dot)com>, "Chris Browne" <cbbrowne(at)acm(dot)org>
Cc: pgsql-performance(at)postgresql(dot)org
Subject: Re: Decide between Postgresql and Mysql (help of
Date: 2006-03-30 21:31:25
Message-ID: op.s68wqnaqcigqcu@apollo13 (view raw, whole thread or download thread mbox)
Lists: pgsql-performance
>> And yes, it does become natural to ask "why not write CGIs in ASM?"
>> ;-)

	Personally, I'd code it in brainfuck, for aesthetic reasons.

> And that, nowadays, is generally the state of web development.  It's not
> the language you're using to write it in, it's how efficiently you're
> using your database.  We can probably tweak the system we're testing now
> and get more from our databases by adjusting how hibernate hits them,
> and the types of queries that it's throwing, but in the long run, the
> bottleneck will always be the database server, because we can throw
> relatively small amounts of money at the other layers if they happen to
> be bogging down.  Not so much with the database.

	So, one wonders why some use 70's languages like Java instead of Lisp or  
Python, which are slower, but a lot more powerful and faster to develop  
	(and don't have hibernate, which is a big bonus)
	(why do you think I don't like Java ?)

In response to


pgsql-performance by date

Next:From: Steinar H. GundersonDate: 2006-03-30 22:36:38
Subject: Re: Decide between Postgresql and Mysql (help of
Previous:From: Gavin HamillDate: 2006-03-30 20:45:31
Subject: Re: CREATE INDEX rather sluggish

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