Re: Planner performance extremely affected by an hanging transaction (20-30 times)?

From: Josh Berkus <josh(at)agliodbs(dot)com>
To: Andres Freund <andres(at)2ndquadrant(dot)com>
Cc: Jeff Janes <jeff(dot)janes(at)gmail(dot)com>, "pgsql-performance(at)postgresql(dot)org" <pgsql-performance(at)postgresql(dot)org>
Subject: Re: Planner performance extremely affected by an hanging transaction (20-30 times)?
Date: 2013-09-27 20:57:02
Message-ID: 5245F11E.20804@agliodbs.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-performance

Andres, Jeff,

>> As far as I can tell, the only downside of doing that is that, since hint
>> bits might be set later, it is possible some dirty pages will get written
>> unhinted and then re-dirtied by the hint bit setting, when more aggressive
>> setting would have only one combined dirty write instead. But that seems
>> rather hypothetical, and if it really is a problem we should probably
>> tackle it directly rather than by barring other optimizations.
>
> I am - as evidenced - too tired to think about this properly, but I
> think you might be right here.

Any thoughts on a fix for this we could get into 9.2.5?

--
Josh Berkus
PostgreSQL Experts Inc.
http://pgexperts.com

In response to

Responses

Browse pgsql-performance by date

  From Date Subject
Next Message Andres Freund 2013-09-27 21:14:39 Re: Planner performance extremely affected by an hanging transaction (20-30 times)?
Previous Message Jim Garrison 2013-09-27 19:57:18 Re: Troubleshooting query performance issues - resolved (sort of)