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

Peripheral Links

Header And Logo

PostgreSQL
| The world's most advanced open source database.

Site Navigation

Search for
  Advanced Search

Re: why postgresql over other RDBMS

  • From: PFC <lists(at)peufeu(dot)com>
  • To: "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us>, "Zoltan Boszormenyi" <zb(at)cybertec(dot)at>
  • Cc: "Harpreet Dhaliwal" <harpreet(dot)dhaliwal01(at)gmail(dot)com>, "Stefan Kaltenbrunner" <stefan(at)kaltenbrunner(dot)cc>, "Alvaro Herrera" <alvherre(at)commandprompt(dot)com>, "Erik Jones" <erik(at)myemma(dot)com>, "Chris Browne" <cbbrowne(at)acm(dot)org>, pgsql-general(at)postgresql(dot)org
  • Subject: Re: why postgresql over other RDBMS
  • Date: Sat, 26 May 2007 21:18:16 +0200
  • Message-id: <op(dot)tsx7wqn5cigqcu(at)apollo13>



MySQL has a related problem, which is that they have embedded IPv4
addressing rather deeply into their client authentication logic (by
making userids be user(at)host not just a username).  This is probably why
they still haven't got IPv6 support:
http://bugs.mysql.com/bug.php?id=8836
I wonder what their plans are for fixing that ...

			regards, tom lane
Well, I have now almost finished my spare-time forum benchmark of MySQL versus Postgres... It was a really interesting experience, and by turning a few stones I discovered some really nasty stuff about MySQL.. well, about InnoDB really. Here's one that you probably didn't know about :
- auto_increment isn't concurrent, this means all inserts into a table which has an auto_increment column are serialized 
	- yes this means INSERT INTO SELECT locks out all other inserts
- the lock is held during ON INSERT TRIGGERS, which means all INSERT TRIGGERs on a given table can't execute concurrently
Home | Main Index | Thread Index

Privacy Policy | PostgreSQL Archives hosted by Command Prompt, Inc. | Designed by tinysofa
Copyright © 1996 – 2008 PostgreSQL Global Development Group