Thanks Tom,
Yes, that did it - it worked after setting enable_mergejoin to off.
mtesfaye@[local](test_db)=# set enable_mergejoin = off;
SET
Time: 0.107 ms
mtesfaye@[local](test_db)=# SELECT DISTINCT(A.*)
FROM table1_t A LEFT JOIN table2_v B
ON A.pnr_id=B.pnr_id
WHERE A.pnr_id IN(1801,2056) AND
Thanks Tom,
I do have a self-contained test case which duplicates the problem. However,
since there are data to be attached and there wasn't a way to attach in the
bug reporting form, I wasn't sure how to proceed.
Would appreciate your assistance.
Thanks again.
On Wed, Sep 26, 2012 at 11:13 PM, T
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_
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
I wrote:
> Argh. The problem query has a plan like this: ...
> which means the indexscan has to support mark/restore calls. And it
> looks like I blew it on mark/restore support when I taught btree to
> handle =ANY conditions natively,
I've committed a patch for this. Thanks for the report!
On 26 September 2012 22:33, wrote:
> The following bug has been logged on the website:
>
> Bug reference: 7572
> Logged by: Daniele Varrazzo
> Email address: daniele.varra...@gmail.com
> PostgreSQL version: 9.1.4
> Operating system: Linux
> Description:
>
> Hello,
>
> when a
The following bug has been logged on the website:
Bug reference: 7573
Logged by: Maxim Boguk
Email address: maxim.bo...@gmail.com
PostgreSQL version: 9.2.0
Operating system: Linux
Description:
Hi,
today while performing migration of test database (with no critical da
Excerpts from Len Tanaka's message of jue sep 27 18:01:30 -0300 2012:
> Thank you for getting back. I noticed an update to 9.2.1. Will add log
> parameter and apply update. DB is not a particularly complex table and
> no foreign wrapping. Machine is older core duo though running OS X
> 10.6.8.
>
>
