Date: Thu, 7 Jul 2005 09:41:47 +0200
To: John A Meinel <john@arbash-meinel.com>
Cc: Postgresql Performance <pgsql-performance@postgresql.org>
Subject: Re: CURSOR slowes down a WHERE clause 100 times?
Message-ID: <20050707074147.GA16360@rigacci.org>
References: <20050706211946.GA3460@rigacci.org>
	<42CC4D1C.9040606@arbash-meinel.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <42CC4D1C.9040606@arbash-meinel.com>
User-Agent: Mutt/1.5.9i
From: Niccolo Rigacci <niccolo@rigacci.org>

> >Can the CURSOR on JOIN affects so heavly the WHERE clause? I
> >suspect that - with the CURSOR - a sequential scan is performed
> >on the entire data set for each fetched record...
> >
> >Any idea?
> >
> >
> What does it say if you do "EXPLAIN ANALYZE SELECT..." both with and
> without the cursor?
> It may not say much for the cursor, but I think you can explain analyze
> the fetch statements.

How can I EXPLAIN ANALYZE a cursor like this?

  BEGIN;
  DECLARE mycursor BINARY CURSOR FOR
    SELECT ...
  FETCH ALL IN mycursor;
  END;

I tried to put EXPLAIN ANALYZE in front of the SELECT and in 
front of the FETCH, but I got two "syntax error"...

Thanks

-- 
Niccolo Rigacci
Firenze - Italy

War against Iraq? Not in my name!