Re: GIN data corruption bug(s) in 9.6devel

From: Tomas Vondra <tomas(dot)vondra(at)2ndquadrant(dot)com>
To: Jeff Janes <jeff(dot)janes(at)gmail(dot)com>
Cc: PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: GIN data corruption bug(s) in 9.6devel
Date: 2015-12-21 19:51:09
Message-ID: 5678582D.3000601@2ndquadrant.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 12/21/2015 07:41 PM, Jeff Janes wrote:
> On Sat, Dec 19, 2015 at 3:19 PM, Tomas Vondra
> <tomas(dot)vondra(at)2ndquadrant(dot)com> wrote:

...

>> So both patches seem to do the trick, but (2) is faster. Not sure
>> if this is expected. (BTW all the results are without asserts
>> enabled).
>
> Do you know what the size of the pending list was at the end of each
> test?
>
> I think last one may be faster because it left a large mess behind
> that someone needs to clean up later.

No. How do I measure it?

>
> Also, do you have the final size of the indexes in each case?

No, I haven't realized the patches do affect that, so I haven't measured it.

regards

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

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Peter Geoghegan 2015-12-21 19:55:50 Re: Re: Reusing abbreviated keys during second pass of ordered [set] aggregates
Previous Message Chapman Flack 2015-12-21 19:30:12 Re: tracking owner of extension-managed objects