Re: GIN data corruption bug(s) in 9.6devel - Mailing list pgsql-hackers

From Tomas Vondra
Subject Re: GIN data corruption bug(s) in 9.6devel
Date
Msg-id 56CF3220.7060402@2ndquadrant.com
Whole thread Raw
In response to Re: GIN data corruption bug(s) in 9.6devel  (Teodor Sigaev <teodor@sigaev.ru>)
List pgsql-hackers
Hi,

On 02/25/2016 05:32 PM, Teodor Sigaev wrote:
>>> Well, turns out there's a quite significant difference, actually. The
>>> index sizes I get (quite stable after multiple runs):
>>>
>>>     9.5 : 2428 MB
>>>     9.6 + alone cleanup : 730 MB
>>>     9.6 + pending lock : 488 MB
>
> In attach modified alone_cleanup patch which doesn't break cleanup
> process as it does pending_lock patch but attached patch doesn't touch a
> lock management.
>
> Tomas. if you can, pls, repeat test with this patch. If not, I will try
> to do it, but later.

I'll do that once the system I used for that gets available - right now 
it's running other benchmarks.

regards

-- 
Tomas Vondra                  http://www.2ndQuadrant.com
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services



pgsql-hackers by date:

Previous
From: Jacek Wielemborek
Date:
Subject: Re: Request for Code Review: BPGSQL
Next
From: "Gabe F. Rudy"
Date:
Subject: FDW handling count(*) through AnalyzeForeignTable or other constant time push-down