Tom Lane wrote:
>
> Jan Wieck <[EMAIL PROTECTED]> 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 c
Jan Wieck <[EMAIL PROTECTED]> 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 the
Christoph Haller wrote:
>
> >
> > Does PostgreSQL optimizer handle iceberg queries well?
> >
> What do you mean by "iceberg query" ?
> I've never heard this term.
Iceberg queries compute one or more aggregate functions to find
aggregate values above a specified threshold. A typical iceberg query
On Tue, Feb 04, 2003 at 09:08:56 -0500,
Wei Weng <[EMAIL PROTECTED]> wrote:
> It is a query that looks like
>
> SELECT target1, target2... targetn, SUN(t.qty)
> FROM Table t
> GROUP BY target1
> HAVING SUM(t.qty)>=10
>
> You can replace SUM(t.qty)>=10 with other aggregate constraints.
There we
TECTED]
Sent: Tuesday, February 04, 2003 3:39 AM
Subject: Re: [SQL] iceberg queries
>
> Does PostgreSQL optimizer handle iceberg queries well?
>
What do you mean by "iceberg query" ?
I've never heard this term.
Regards, Christoph
--
>
> Does PostgreSQL optimizer handle iceberg queries well?
>
What do you mean by "iceberg query" ?
I've never heard this term.
Regards, Christoph
---(end of broadcast)---
TIP 1: subscribe and unsubscribe commands go to [EMAIL PROTECTED]
Does PostgreSQL optimizer handle iceberg queries well?
Thanks
Wei
---(end of broadcast)---
TIP 1: subscribe and unsubscribe commands go to [EMAIL PROTECTED]
