Ole Tange <[EMAIL PROTECTED]> writes:
> Now I am curious: Why isn't DISTINCT implemented using a Hash aggregate?
Partly lack of round tuits, partly the fact that it is closely
intertwined with ORDER BY and I'm not sure what side-effects would
arise from separating them. In particular, the DISTINC
On Sun, 15 Aug 2004, Tom Lane wrote:
> Ole Tange <[EMAIL PROTECTED]> writes:
> > As I read it the output tells me what was done during the milliseconds:
>
> No, you have a fundamental misconception here. The notation means that
> the first output row from a plan step was delivered after X
> mill
On Sun, Aug 15, 2004 at 07:47:53PM +0200, Ole Tange wrote:
> QUERY PLAN
> -
> Unique (cost=5680.00..5766.70 rows=8670 width=26) (act
Ole Tange <[EMAIL PROTECTED]> writes:
> As I read it the output tells me what was done during the milliseconds:
No, you have a fundamental misconception here. The notation means that
the first output row from a plan step was delivered after X
milliseconds, and the last row after Y milliseconds.
Using this SQL:
EXPLAIN ANALYZE
SELECT DISTINCT
sessionid,
'2004-33' AS "yearweek",
nd.niveau
INTO TEMP
distinct_session
FROM
httplog h ,niveaudir nd
WHERE
hitDateTime>('now'::timestamp with time zone-'1440 min'::interval)
and h.hostid=(selec
