Re: Hashagg planning bug (8.0.1)

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Rod Taylor <pg(at)rbt(dot)ca>
Cc: PostgreSQL Development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Hashagg planning bug (8.0.1)
Date: 2005-05-10 16:11:05
Message-ID: 3325.1115741465@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Rod Taylor <pg(at)rbt(dot)ca> writes:
> It would seem that the planner does not take into account whether the
> datatypes involved have the capability to use hash aggregates or not.

> sdb=# explain select query_start, current_query from pg_locks join stat_activity on pid = procpid where granted = true and transaction in (select transaction from pg_locks where granted = false);
> ERROR: could not find hash function for hash operator 716373

What's stat_activity? I thought you meant pg_stat_activity, but that
works fine here.

regards, tom lane

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Rod Taylor 2005-05-10 16:21:45 Re: Hashagg planning bug (8.0.1)
Previous Message Christopher Kings-Lynne 2005-05-10 15:35:42 Re: Please clarify