Re: [HACKERS] Hashagg planning bug (8.0.1)

2005-05-11 Thread Hannu Krosing
On T, 2005-05-10 at 13:17 -0400, Tom Lane wrote: > Rod Taylor <[EMAIL PROTECTED]> writes: > > It's the = operator that Slony adds for xxid comparisons. I didn't even > > think of changes Slony would have made. > > > ssdb=# select * from pg_operator where oid = 716373; > > oprname | oprnamespace |

Re: [HACKERS] Hashagg planning bug (8.0.1)

2005-05-10 Thread Tom Lane
Rod Taylor <[EMAIL PROTECTED]> writes: > It's the = operator that Slony adds for xxid comparisons. I didn't even > think of changes Slony would have made. > ssdb=# select * from pg_operator where oid = 716373; > oprname | oprnamespace | oprowner | oprkind | oprcanhash | oprleft | > oprright | op

Re: [HACKERS] Hashagg planning bug (8.0.1)

2005-05-10 Thread Rod Taylor
On Tue, 2005-05-10 at 12:50 -0400, Tom Lane wrote: > Rod Taylor <[EMAIL PROTECTED]> writes: > > Oh, stat_activity is a view which removes idle connections from > > displaying and allows non-privileged users to see everything that's > > going on within the DB. > > Still works fine for me. Do you e

Re: [HACKERS] Hashagg planning bug (8.0.1)

2005-05-10 Thread Tom Lane
Rod Taylor <[EMAIL PROTECTED]> writes: > Oh, stat_activity is a view which removes idle connections from > displaying and allows non-privileged users to see everything that's > going on within the DB. Still works fine for me. Do you even have an operator 716373? If so what is it?

Re: [HACKERS] Hashagg planning bug (8.0.1)

2005-05-10 Thread Rod Taylor
On Tue, 2005-05-10 at 12:11 -0400, Tom Lane wrote: > Rod Taylor <[EMAIL PROTECTED]> 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

Re: [HACKERS] Hashagg planning bug (8.0.1)

2005-05-10 Thread Tom Lane
Rod Taylor <[EMAIL PROTECTED]> 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

[HACKERS] Hashagg planning bug (8.0.1)

2005-05-10 Thread Rod Taylor
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 transactio