pg.ddx.io  pgsql-sql@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Jan Wieck <JanWieck@Yahoo.com>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: Christoph Haller <ch@rodos.fzk.de>
Cc: pgsql-sql@postgresql.org
Cc: wweng@kencast.com
Subject: Re: iceberg queries
Date: Tue, 04 Feb 2003 18:14:02 -0500
Message-ID: <3E40493A.DCDD2C4B@Yahoo.com> (raw)
References: <3E3F7C59.E6C5278C@rodos.fzk.de>
	<3E40011C.94F11C92@Yahoo.com>
	<15716.1044383829@sss.pgh.pa.us>

Tom Lane wrote:
> 
> Jan Wieck <JanWieck@Yahoo.com> writes:
> > As to the original question, if an index is available that returns the
> > rows in the sort order of the GROUP BY clause, PostgreSQL defaults to an
> > index scan, otherwise it will do a sort of the rows matching an optional
> > WHERE clause. This sorted set is then grouped and aggregated and
> > filtered by the HAVING clause after aggregation.
> 
> Note that as of 7.4, the planner will probably pick hashed aggregation
> rather than sort-based aggregation, if it can predict that the number
> of groups will not be too large for a hash table to fit in memory.
> This means we can do a seqscan (or, perhaps, an indexscan to match
> WHERE conditions) and avoid sorting.  So I expect performance on this
> type of query to be a good deal better in 7.4.  There are a few
> benchmark comparisons in the pghackers archives a couple months back.
> 
>                         regards, tom lane

If it can predict.

I guess the question was asked because one expects performance problems.
From that I conclude that the amount of data is significant in this
particular case. That does not necessarily but usually mean a large
number of unique groups.


Jan

-- 
#======================================================================#
# It's easier to get forgiveness for being wrong than for being right. #
# Let's break this rule - forgive me.                                  #
#================================================== JanWieck@Yahoo.com #



view thread (7+ messages)

Message-ID: <3E40493A.DCDD2C4B@Yahoo.com>
Permalink:  ../3E40493A.DCDD2C4B@Yahoo.com/
Also on:    postgresql.org/message-id/3E40493A.DCDD2C4B@Yahoo.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-sql@postgresql.org
  Cc: JanWieck@Yahoo.com, tgl@sss.pgh.pa.us, ch@rodos.fzk.de, wweng@kencast.com
  Subject: Re: iceberg queries
  In-Reply-To: <3E40493A.DCDD2C4B@Yahoo.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