Re: Guidelines for GSoC student proposals / Eliminate O(N^2) scaling from rw-conflict tracking in serializable transactions

From: Kevin Grittner <kgrittn(at)gmail(dot)com>
To: Mengxing Liu <liu-mx15(at)mails(dot)tsinghua(dot)edu(dot)cn>
Cc: "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Guidelines for GSoC student proposals / Eliminate O(N^2) scaling from rw-conflict tracking in serializable transactions
Date: 2017-03-30 15:22:20
Message-ID: CACjxUsNnf=NkeHWFD1Bo71TUfTWX7FaCghHBL3uvSsR5OZtABw@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Wed, Mar 29, 2017 at 11:17 PM, Mengxing Liu
<liu-mx15(at)mails(dot)tsinghua(dot)edu(dot)cn> wrote:
> Thanks, I've updated the proposal. Just one issue:
> I agree that we can make skip list a general data structure. But
> can we use the fixed-level skip list as a Plan B? Or a quick attempt
> before the general data structure ?
> Because I am not familiar with shared memory structure and tricks
> used in it, and I cannot estimate how much time it would take.

It's not really too bad for fixed allocation shared memory, and I
can help with that. If I thought it would save much I could see
doing a prototype without generalization, but you would still have
most of the same shared memory issues, since the structure *must*
live in shared memory.

--
Kevin Grittner

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Teodor Sigaev 2017-03-30 15:25:38 Re: WIP: Covering + unique indexes.
Previous Message Alexander Korotkov 2017-03-30 15:09:51 Re: Re: proposal - psql: possibility to specify sort for describe commands, when size is printed