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

From: "Mengxing Liu" <liu-mx15(at)mails(dot)tsinghua(dot)edu(dot)cn>
To: "Kevin Grittner" <kgrittn(at)gmail(dot)com>
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-31 01:41:43
Message-ID: 47348989.1e3c.15b22068020.Coremail.liu-mx15@mails.tsinghua.edu.cn
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers


> > 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.
>

Thank you. If there is no other problem, I will submit the proposal.

--
Mengxing Liu

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Amit Langote 2017-03-31 02:13:03 tuple-routing and constraint violation error message, revisited
Previous Message Petr Jelinek 2017-03-31 00:53:16 Re: Somebody has not thought through subscription locking considerations