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

help / color / mirror / Atom feed
From: Sean Chittenden <sean@chittenden.org>
To: nolan@celery.tssi.com
Cc: Jan Wieck <JanWieck@Yahoo.com>
Cc: Bruce Momjian <pgman@candle.pha.pa.us>
Cc: Josh Berkus <josh@agliodbs.com>
Cc: Joe Conway <mail@joeconway.com>
Cc: \"Advocacy PostgreSQL\" <pgsql-advocacy@postgresql.org>
Cc: PostgreSQL-general <pgsql-general@postgresql.org>
Subject: Re: [GENERAL] interesting PHP/MySQL thread
Date: Sun, 22 Jun 2003 20:07:02 -0700
Message-ID: <20030623030702.GM97131@perrin.int.nxad.com> (raw)
In-Reply-To: <20030623025439.28324.qmail@celery.tssi.com>
References: <3EF655E7.9070709@Yahoo.com>
	<20030623025439.28324.qmail@celery.tssi.com>

> I know it took me a while to convince the CIO on the project I'm working
> on that PostgreSQL was an improvement over MySQL.  He's slowly coming
> around as I start to show him what I am doing with the much richer 
> PostgreSQL feature set, but the performance of 7.3 compared to MySQL is 
> likely to remain a bit of a sticking point, because some queries are 
> taking 2-3 times as long on the same platform with the same data.
> 
> If the data entry folks, who are probably about to get a look at a portion 
> of the application that is still using the MySQL engine, get used to the 
> search times there, when we switch the whole thing over to PostgreSQL we 
> may get complaints if searches that used to take 3-4 seconds are now 
> taking 10-12 seconds.  (Have others noticed that 7 seconds seems to be 
> a threshold point for users reacting to query times?)

Whoa, something's not right.  Could you please send along an EXPLAIN
ANALYZE after doing a VACUUM ANALYZE of your query that's taking 3-4x
longer?  Something smells very strange here because my experience has
been quite the opposite...  I can understand 0.05ms longer per
connection in setup overhead (fork() vs new thread) , but this seems
like way too much... I wonder if you couldn't benefit from the use of
a cursor if you're returning a large dataset.  -sc

http://developer.postgresql.org/docs/postgres/sql-declare.html
http://developer.postgresql.org/docs/postgres/sql-fetch.html
http://developer.postgresql.org/docs/postgres/sql-close.html

-- 
Sean Chittenden



view thread (72+ messages)  latest in thread

Message-ID: <20030623030702.GM97131@perrin.int.nxad.com>
Permalink:  ../20030623030702.GM97131@perrin.int.nxad.com/
Also on:    postgresql.org/message-id/20030623030702.GM97131@perrin.int.nxad.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-docs@postgresql.org
  Cc: sean@chittenden.org, nolan@celery.tssi.com, JanWieck@Yahoo.com, pgman@candle.pha.pa.us, josh@agliodbs.com, mail@joeconway.com, pgsql-advocacy@postgresql.org, pgsql-general@postgresql.org
  Subject: Re: [GENERAL] interesting PHP/MySQL thread
  In-Reply-To: <20030623030702.GM97131@perrin.int.nxad.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