2012/9/27 Radovan Jablonovsky :
> Hi Pavel,
>
> Here are the test data with set enable_hashagg to off. It does not looks
> like improvement. Query was running for 30min without returning result set.
so maybe it is PostgreSQL bug - probably window function doesn't reset
some memory context and then
Hi Pavel,
Here are the test data with set enable_hashagg to off. It does not looks
like improvement. Query was running for 30min without returning result set.
db=> set enable_hashagg=off;
SET
db=> explain
db-> SELECT
db-> schema_name,
db-> sum(table_size)
db-> FROM
db-> (SELECT
db(> pg_
Hello
you should to run this query on real data - and if it works now, then
send EXPLAIN ANALYZE result, please
Pavel
2012/9/27 Melese Tesfaye :
> Thanks Pavel,
> Setting enable_hashagg to off didn't resolve the issue.
> Please find the explain as well as query results after "set
> enable_hashag
Thanks Pavel,
Setting enable_hashagg to off didn't resolve the issue.
Please find the explain as well as query results after "set
enable_hashagg=off;"
mtesfaye@[local](test_db)=# EXPLAIN SELECT DISTINCT(A.*)
test_db-# FROM table1_t A LEFT JOIN table2_v B
test_db-# ON A.pnr_id=B.pnr_id
test_db-# WH
Hello
this situation is possible, when optimizer use HashAgg where should not use it.
Please, try to disable HashAgg - set enable_hashagg to off;
please, send EXPLAIN result
Regards
Pavel Stehule
2012/9/26 :
> The following bug has been logged on the website:
>
> Bug reference: 7571
> L
The following bug has been logged on the website:
Bug reference: 7571
Logged by: Radovan Jablonovsky
Email address: radovan.jablonov...@replicon.com
PostgreSQL version: 9.1.5
Operating system: CentOs 5.8 Linux 2.6.18-308.el5 x86_64
Description:
During checking our co
