From: Tom Lane <tgl@sss.pgh.pa.us>
To: Scott Marlowe <smarlowe@g2switchworks.com>
Cc: Alvaro Herrera <alvherre@commandprompt.com>
Cc: andremachado <andremachado@techforce.com.br>
Cc: pgsql-performance@postgresql.org
Subject: Re: firebird X postgresql 8.1.2 windows, performance
Date: Tue, 07 Mar 2006 14:56:45 -0500
Message-ID: <2876.1141761405@sss.pgh.pa.us> (raw)
In-Reply-To: <1141751939.18820.174.camel@state.g2switchworks.com>
References: <20060307162842.M37264@techforce.com.br>
<1141751333.18820.172.camel@state.g2switchworks.com>
<20060307171514.GE6748@surnet.cl>
<1141751939.18820.174.camel@state.g2switchworks.com>
Scott Marlowe <smarlowe@g2switchworks.com> writes:
> So, do you see any obvious, low hanging fruit here?
It would help if we were being told the whole truth about the settings
being used. The first few plans are clearly suffering from the
"enable_seqscan = off" error, but the last few don't seem to be. I
don't trust the SHOW ALL at all since it disagrees with the immediately
following retail SHOWs --- there is seemingly a whole lot of parameter
changing going on that we are not being told about.
It'd also be a good idea to know something about the datatypes involved,
particularly for the join keys.
regards, tom lane
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: tgl@sss.pgh.pa.us, smarlowe@g2switchworks.com, alvherre@commandprompt.com, andremachado@techforce.com.br
Subject: Re: firebird X postgresql 8.1.2 windows, performance
In-Reply-To: <2876.1141761405@sss.pgh.pa.us>
* 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