Re: Handling GIN incomplete splits

On 12/01/2013 10:40 PM, Jeff Janes wrote:
> On Wed, Nov 27, 2013 at 9:40 AM, Jeff Janes <jeff.janes@gmail.com> wrote:
>
>> The commit 04eee1fa9ee80dabf7 of this series causes a self-deadlock in the
>> LWLock code during the operation below, with it trying to take
>> an LW_EXCLUSIVE on a high, even-numbered lockid when it already holds the
>> same lockid.
>>
>> CREATE INDEX planet_osm_ways_nodes ON planet_osm_ways USING gin (nodes)
>>   WITH (FASTUPDATE=OFF);
>>
>> It happens pretty reliably using osm2pgsql.
>>
>> I will try to come up with a simple reproducible demonstration, and stack
>> trace, over the weekend.
>
> Whatever the problem, it seems to have been fixed in ce5326eed386959aa,
> "More GIN refactoring".

That's good, I guess :-). Thanks for the testing. Did you import the 
full planet.osm? I tried with a subset containing just Finland, but 
didn't see any problems.

- Heikki