pg.ddx.io  pgsql-performance@postgresql.org mailing list archive  

help / color / mirror / Atom feed
From: Greg Smith <gsmith@gregsmith.com>
To: pgsql-performance@postgresql.org
Subject: Re: Feature Request --- was: PostgreSQL Performance Tuning
Date: Tue, 1 May 2007 21:52:16 -0400 (EDT)
Message-ID: <Pine.GSO.4.64.0705012134370.24215@westnet.com> (raw)
In-Reply-To: <33127762-7EBB-4D1E-9147-5BFB3EB7A883@earlham.edu>
References: <OFC96167D5.6BB63AC2-ON652572C9.003B5263-652572C9.003E4142@lntinfotech.com>
	<20070427143023.GA2422@mathom.us>
	<46323744.5020703@drivefaster.net>
	<200704271059.50265.josh@agliodbs.com>
	<Pine.GSO.4.64.0704292241270.1296@westnet.com>
	<463616EB.3040800@modgraph-usa.com>
	<33127762-7EBB-4D1E-9147-5BFB3EB7A883@earlham.edu>

On Mon, 30 Apr 2007, Kevin Hunter wrote:

> I recognize that PostgreSQL and MySQL try to address different 
> problem-areas, but is this one reason why a lot of people with whom I 
> talk prefer MySQL? Because PostgreSQL is so "slooow" out of the box?

It doesn't help, but there are many other differences that are as big or 
bigger.  Here are a few samples off the top of my head:

1) Performance issues due to MVCC (MySQL fans love to point out how 
fast they can do select count(*) from x)
2) Not knowing you have to run vacuum analyze and therefore never seeing a 
good query result
3) Unfair comparison of PostgreSQL with robust WAL vs. MySQL+MyISAM on 
write-heavy worksloads

These are real issues, which of course stack on top of things like 
outdated opinions from older PG releases with performance issues resolved 
in the last few years.

--
* Greg Smith gsmith@gregsmith.com http://www.gregsmith.com Baltimore, MD



view thread (53+ messages)  latest in thread

Message-ID: <Pine.GSO.4.64.0705012134370.24215@westnet.com>
Permalink:  ../Pine.GSO.4.64.0705012134370.24215@westnet.com/
Also on:    postgresql.org/message-id/Pine.GSO.4.64.0705012134370.24215@westnet.com

 · 

reply
Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: pgsql-performance@postgresql.org
  Cc: gsmith@gregsmith.com
  Subject: Re: Feature Request --- was: PostgreSQL Performance Tuning
  In-Reply-To: <Pine.GSO.4.64.0705012134370.24215@westnet.com>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox