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: 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 21:22:59 -0700
Message-ID: <20030623042259.GQ97131@perrin.int.nxad.com> (raw)
In-Reply-To: <20030623035501.251.qmail@celery.tssi.com>
References: <20030623030702.GM97131@perrin.int.nxad.com>
	<20030623035501.251.qmail@celery.tssi.com>

> > 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?
> 
> As luck would have it, I just finished the latest 'emergency' part
> of the project, so I may have a day or so to play with this before
> the CIO figures out I'm done.  :-)
> 
> I'm hoping this turns out to be a tuning issue, as I'm still very
> much of a rookie at tuning PostgreSQL.
> 
> I'll see if I can work something up.  Should this go to the general
> list or somewhere else?

Definitely performance@.  -sc

-- 
Sean Chittenden



view thread (72+ messages)  latest in thread

Message-ID: <20030623042259.GQ97131@perrin.int.nxad.com>
Permalink:  ../20030623042259.GQ97131@perrin.int.nxad.com/
Also on:    postgresql.org/message-id/20030623042259.GQ97131@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, pgsql-advocacy@postgresql.org, pgsql-general@postgresql.org
  Subject: Re: [GENERAL] interesting PHP/MySQL thread
  In-Reply-To: <20030623042259.GQ97131@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