From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | typedeath(at)zipmail(dot)com(dot)br |
Cc: | pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: Is it a bug? |
Date: | 2000-02-19 00:14:51 |
Message-ID: | 4560.950919291@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
"Mauricio da Silva Barrios" <typedeath(at)zipmail(dot)com(dot)br> writes:
> mydb=> CREATE VIEW connection_last AS
> SELECT * FROM connection as con_out
> WHERE connection_start IN ( SELECT max(connection_start) FROM
> connection as con_in
> WHERE con_in.connection_owner =
> con_out.connection_owner
> GROUP BY connection_owner);
> mydb=> select * from connection_last;
> pqReadData() -- backend closed the channel unexpectedly.
Hmm. Seems to work fine in current sources:
regression=# select * from connection_last;
connection_id | connection_owner | connection_start | connection_end
---------------+------------------+------------------------+----------------
3 | 2 | 2001-01-22 00:00:00-05 | 00:02:02
(1 row)
I seem to recall that the rule rewriter had some problems dealing with
aggregate functions inside sub-selects in 6.5.*, and that's probably
what's causing your problem.
7.0 is scheduled to go beta next week, so I'd suggest picking up
a beta copy ...
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2000-02-19 00:21:50 | Re: [HACKERS] Re: SQL compliance - why -- comments only at psql level ? |
Previous Message | Tom Lane | 2000-02-19 00:00:18 | Re: [HACKERS] queries on 2+ indices |