Re: [HACKERS] GSOC Introduction / Eliminate O(N^2) scaling from rw-conflict tracking in serializable transactions

[Stephen Frost]

George,

* George Papadrosou (gpapadro...@gmail.com) wrote:
> I understand your efforts and I am willing to back down. This is not the only 
> project that appeals to me :)

Thank you very much for your willingness to adapt. :)

> Mr. Frost, Mr. Munro,  thank you for your suggestions. I am now between the 
> TOAST’ing slices and the predicate locking project. I am keen on the fact the 
> “toasting” project is related to on-disk data structures so I will probably 
> send you an email about that later today.

I don't recall seeing an email from you about this yet?  My apologies if
I missed it.  I have added Alexander Korotkov to the CC list as he was
also listed as a possible mentor for TOAST'ing in slices.

As it relates to TOAST'ing in slices, it would be good to think through
how we would represent and store the information about how a particular
object has been split up.  Note that PostgreSQL is very extensible in
its type system and therefore we would need a way for new data types
which are added to the system to be able to define how data of that data
type is to be split and a way to store the information they need to
regarding such a split.

In particular, the PostGIS project adds multiple data types which are
variable in length and often end up TOAST'd because they are large
geospatial objects, anything we come up with for TOAST'ing in slices
will need to be something that the PostGIS project could leverage.

> In general, I would like to undertake a project interesting enough and 
> important for Postgres. Also, I could take into account if you favor one over 
> another, so please let me know. I understand that these projects should be 
> strictly defined to fit in the GSOC period, however the potential for future 
> improvements or challenges is what drives and motivates me.

We are certainly very interested in having you continue on and work with
the PostgreSQL community moving forward, though we do need to be sure to
scope the project goals within the GSOC requirements.

Thanks!

Stephen


signature.asc
Description: Digital signature

Re: [HACKERS] GSOC Introduction / Eliminate O(N^2) scaling from rw-conflict tracking in serializable transactions

[George Papadrosou]

Hi all and thank you for your quick replies.

> [two people interested in the same GSoC project]

Mr. Grittner thank you for sharing this ahead of time.


Liu(is this your first name?),

> I have been concentrating on it for a long time, reading papers, reading 
> source codes, and discussing details with Mr Grittner.  

I understand your efforts and I am willing to back down. This is not the only 
project that appeals to me :)


Mr. Frost, Mr. Munro,  thank you for your suggestions. I am now between the 
TOAST’ing slices and the predicate locking project. I am keen on the fact the 
“toasting” project is related to on-disk data structures so I will probably 
send you an email about that later today.

In general, I would like to undertake a project interesting enough and 
important for Postgres. Also, I could take into account if you favor one over 
another, so please let me know. I understand that these projects should be 
strictly defined to fit in the GSOC period, however the potential for future 
improvements or challenges is what drives and motivates me.

Thank you!
George




-- 
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers

Re: [HACKERS] GSOC Introduction / Eliminate O(N^2) scaling from rw-conflict tracking in serializable transactions

[Stephen Frost]

Kevin,

* Kevin Grittner (kgri...@gmail.com) wrote:
> > [two people interested in the same GSoC project]
> 
> It's an interesting problem to have.
> 
> If neither of you chooses to voluntarily back down, the obvious
> resolution is for the mentors to vote on the better proposal.  If we
> do that early enough during the student application period, there
> might still be time for the person whose proposal wasn't chosen to
> submit a proposal for an alternative project.  As I see it, that
> means:
> 
>  - I would tend to favor a proposal submitted on the first day
>(beginning March 20 16:00 UTC), if only one is.
> 
>  - I would push for very early voting by the PostgreSQL mentors.

Agreed.  Many thanks!

Stephen


signature.asc
Description: Digital signature

Re: [HACKERS] GSOC Introduction / Eliminate O(N^2) scaling from rw-conflict tracking in serializable transactions

[Kevin Grittner]

> [two people interested in the same GSoC project]

It's an interesting problem to have.

If neither of you chooses to voluntarily back down, the obvious
resolution is for the mentors to vote on the better proposal.  If we
do that early enough during the student application period, there
might still be time for the person whose proposal wasn't chosen to
submit a proposal for an alternative project.  As I see it, that
means:

 - I would tend to favor a proposal submitted on the first day
   (beginning March 20 16:00 UTC), if only one is.

 - I would push for very early voting by the PostgreSQL mentors.

--
Kevin Grittner


-- 
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers

Re: [HACKERS] GSOC Introduction / Eliminate O(N^2) scaling from rw-conflict tracking in serializable transactions

[Mengxing Liu]

Hi George, 

I am Mengxing Liu. Happy to meet someone with the same idea : )

I have been concentrating on it for a long time, reading papers, reading source 
codes, and discussing details with Mr Grittner.  So I really understand your 
passion on it. But definitely I don't want all these effects to be in vain. So, 
maybe a little ruthless, would you mind to consider transferring to the other 
one?


> -原始邮件-
> 发件人: "Kevin Grittner" <kgri...@gmail.com>
> 发送时间: 2017-03-10 22:57:03 (星期五)
> 收件人: "George Papadrosou" <gpapadro...@gmail.com>, "刘梦醒" 
> <liu-m...@mails.tsinghua.edu.cn>
> 抄送: "pgsql-hackers@postgresql.org" <pgsql-hackers@postgresql.org>
> 主题: Re: [HACKERS] GSOC Introduction / Eliminate O(N^2) scaling from 
> rw-conflict tracking in serializable transactions
> 
> [including Mengxing Liu in response, for reasons that should become
> obvious below...]
> 
> Hi George,
> 
> On Thu, Mar 9, 2017 at 6:49 PM, George Papadrosou <gpapadro...@gmail.com> 
> wrote:
> 
> > my name is George Papadrosou, this is my first semester as
> > graduate student at Georgia Tech and would like to submit a
> > proposal to Google Summer of Code, for the project "Eliminate
> > O(N^2) scaling from rw-conflict tracking in serializable
> > transactions”.
> 
> I was recently contacted off-list by Mengxing Liu, who has been
> looking at the same project, and said he was planning to submit a
> GSoC proposal.  Rather than have one of you sit this out, do either
> of you feel comfortable taking a different project instead?  Since
> you've both been looking at the serializable code and supporting
> documents, perhaps one of you could change to the other suggested
> Serializable project?
> 
> > I am going to prepare a draft proposal for this project and share
> > it with you soon. The project’s description is pretty clear, do
> > you think it should be more strictly defined in the proposal?
> 
> At a minimum, the proposal should include list of milestones you
> expect to reach along the way, and a timeline indicating when you
> expect to reach them.  Some description of the benchmarks you intend
> to run would be also be very good.
> 
> > Until then, I would like to familiarize myself a bit with the
> > codebase and fix some bug/todo. I didn’t find many [E] marked
> > tasks in the todo list so the task I was thinking is "\s without
> > arguments (display history) fails with libedit, doesn't use pager
> > either - psql \s not working on OSX”. However, it works on my OSX
> > El Capitan laptop with Postgres 9.4.4. Would you suggest some
> > other starter task?
> 
> There is a CommitFest in progress; reviewing patches is a good way
> to become involved and familiar with the community processes.
> 
> https://wiki.postgresql.org/wiki/CommitFest
> 
> --
> Kevin Grittner


--
Mengxing Liu










-- 
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers

Re: [HACKERS] GSOC Introduction / Eliminate O(N^2) scaling from rw-conflict tracking in serializable transactions

[Kevin Grittner]

[including Mengxing Liu in response, for reasons that should become
obvious below...]

Hi George,

On Thu, Mar 9, 2017 at 6:49 PM, George Papadrosou  wrote:

> my name is George Papadrosou, this is my first semester as
> graduate student at Georgia Tech and would like to submit a
> proposal to Google Summer of Code, for the project "Eliminate
> O(N^2) scaling from rw-conflict tracking in serializable
> transactions”.

I was recently contacted off-list by Mengxing Liu, who has been
looking at the same project, and said he was planning to submit a
GSoC proposal.  Rather than have one of you sit this out, do either
of you feel comfortable taking a different project instead?  Since
you've both been looking at the serializable code and supporting
documents, perhaps one of you could change to the other suggested
Serializable project?

> I am going to prepare a draft proposal for this project and share
> it with you soon. The project’s description is pretty clear, do
> you think it should be more strictly defined in the proposal?

At a minimum, the proposal should include list of milestones you
expect to reach along the way, and a timeline indicating when you
expect to reach them.  Some description of the benchmarks you intend
to run would be also be very good.

> Until then, I would like to familiarize myself a bit with the
> codebase and fix some bug/todo. I didn’t find many [E] marked
> tasks in the todo list so the task I was thinking is "\s without
> arguments (display history) fails with libedit, doesn't use pager
> either - psql \s not working on OSX”. However, it works on my OSX
> El Capitan laptop with Postgres 9.4.4. Would you suggest some
> other starter task?

There is a CommitFest in progress; reviewing patches is a good way
to become involved and familiar with the community processes.

https://wiki.postgresql.org/wiki/CommitFest

--
Kevin Grittner


-- 
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers

Re: [HACKERS] GSOC Introduction / Eliminate O(N^2) scaling from rw-conflict tracking in serializable transactions

[Thomas Munro]

On Fri, Mar 10, 2017 at 2:04 PM, Stephen Frost  wrote:
> George,
>
> * George Papadrosou (gpapadro...@gmail.com) wrote:
>> my name is George Papadrosou, this is my first semester as graduate student 
>> at Georgia Tech and would like to submit a proposal to Google Summer of 
>> Code, for the project "Eliminate O(N^2) scaling from rw-conflict tracking in 
>> serializable transactions”.
>
> Fantastic!  I'll let Kevin comment on your questions regarding that
> project.

+1, welcome.  It would be very cool to see SERIALIZABLE get faster.

>> Until then, I would like to familiarize myself a bit with the codebase and 
>> fix some bug/todo. I didn’t find many [E] marked tasks in the todo list so 
>> the task I was thinking is "\s without arguments (display history) fails 
>> with libedit, doesn't use pager either - psql \s not working on OSX”. 
>> However, it works on my OSX El Capitan laptop with Postgres 9.4.4. Would you 
>> suggest some other starter task?
>
> One of the best things which you can do to start learning the PostgreSQL
> code base is to review existing patches which have been proposed for
> inclusion.  Now is a great time to be doing that as the feature freeze
> for the next version of PostgreSQL (PG v10) is at the end of the month
> and there's a ton of patches which need reviewing.
>
> The patches which need reviewing can be seen here:
>
> https://commitfest.postgresql.org/13/

+1

This is a large commitfest so there's a pretty wide range of
interesting stuff to help out with, and many ways to help including
documentation, testing and code review.


One small patch that just might interest you, based on your interest
in SERIALIZABLE and also in parallelism, is my fledgling attempt to
connect those two features:

https://commitfest.postgresql.org/13/1004/

Unfortunately SERIALIZABLE support has not yet been included with a
couple of really important recent Postgres features: parallelism and
streaming replication.  I suspect the latter may be quite hard to fix
and the former quite easy.  If you're currently studying the
SERIALIZABLE internal data structures then you might like to review
that patch and tell me if my optimism is entirely misplaced, and
figure out how to test and break it...


That said, please pick anything that interests you!

-- 
Thomas Munro
http://www.enterprisedb.com


-- 
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers

Re: [HACKERS] GSOC Introduction / Eliminate O(N^2) scaling from rw-conflict tracking in serializable transactions

[Stephen Frost]

George,

* George Papadrosou (gpapadro...@gmail.com) wrote:
> my name is George Papadrosou, this is my first semester as graduate student 
> at Georgia Tech and would like to submit a proposal to Google Summer of Code, 
> for the project "Eliminate O(N^2) scaling from rw-conflict tracking in 
> serializable transactions”.

Fantastic!  I'll let Kevin comment on your questions regarding that
project.

> Until then, I would like to familiarize myself a bit with the codebase and 
> fix some bug/todo. I didn’t find many [E] marked tasks in the todo list so 
> the task I was thinking is "\s without arguments (display history) fails with 
> libedit, doesn't use pager either - psql \s not working on OSX”. However, it 
> works on my OSX El Capitan laptop with Postgres 9.4.4. Would you suggest some 
> other starter task?

One of the best things which you can do to start learning the PostgreSQL
code base is to review existing patches which have been proposed for
inclusion.  Now is a great time to be doing that as the feature freeze
for the next version of PostgreSQL (PG v10) is at the end of the month
and there's a ton of patches which need reviewing.

The patches which need reviewing can be seen here:

https://commitfest.postgresql.org/13/

There's lots of information on our wiki and other places about
developing PostgreSQL, you can start here:

https://wiki.postgresql.org/wiki/Development_information

and in particular:

https://wiki.postgresql.org/wiki/So,_you_want_to_be_a_developer%3F

We look forward to working with you!  Welcome!

Thanks!

Stephen


signature.asc
Description: Digital signature

[HACKERS] GSOC Introduction / Eliminate O(N^2) scaling from rw-conflict tracking in serializable transactions

[George Papadrosou]

Hello psql hackers,

my name is George Papadrosou, this is my first semester as graduate student at 
Georgia Tech and would like to submit a proposal to Google Summer of Code, for 
the project "Eliminate O(N^2) scaling from rw-conflict tracking in serializable 
transactions”.

A short bio, I have a CS undergraduate degree from Athens University of 
Economics and Business. I had taken two databases courses where the first one 
was about sql, relational algebra, xpath and generally using an RDBMS while the 
second one was more about the internals, like  storage, indexing, query 
planning and transactions.

I have 3+ years professional experience in web technologies with a focus on the 
backend and I recently started my master with specialization in computing 
systems. One of my first courses that I am finishing this May is High 
Performance Computing(parallel algorithms), which seems to be closely related 
to this GSOC project.

I have not done any research on databases yet but I regard this project as an 
opportunity to make an initial contact with postgres' internals until I dive 
more into database algorithms. My future goal is to work on databases full
time.

I am going to prepare a draft proposal for this project and share it with you 
soon. The project’s description is pretty clear, do you think it should be more 
strictly defined in the proposal?

Until then, I would like to familiarize myself a bit with the codebase and fix 
some bug/todo. I didn’t find many [E] marked tasks in the todo list so the task 
I was thinking is "\s without arguments (display history) fails with libedit, 
doesn't use pager either - psql \s not working on OSX”. However, it works on my 
OSX El Capitan laptop with Postgres 9.4.4. Would you suggest some other starter 
task?

Looking forward to hearing from you soon.
Best regards,
George


-- 
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers