On Mar 26, 2011, at 12:24 PM, Tom Lane <t...@sss.pgh.pa.us> wrote:
> Simon Riggs <si...@2ndquadrant.com> writes:
>> On Sat, Mar 26, 2011 at 4:04 PM, Tom Lane <t...@sss.pgh.pa.us> wrote:
>>> In particular, in view of today's fix, shouldn't this commit be reverted?
>>> 
>>> http://git.postgresql.org/gitweb?p=postgresql.git;a=commitdiff;h=6e8e7cc580665ddd43c8ca2acc6d60f345570a57
>>> 
>>> I thought at the time that that was nothing more than documenting a
>>> known bug, and now it is documenting a dead bug.
> 
>> No, that doc change is still accurate.
> 
> Well, in that case, it should be on the open-items list.  If the system
> is still behaving that way, it's a bug.

I suspect it's fixed, but I haven't checked yet.

And contrary to Simon's contention on a nearby email, it was not a "slight" 
performance degradation. It was running at like 1 tps.

...Robert
-- 
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers

Reply via email to