GSoC 2014 - mentors, students and admins

Started by Thom Brownabout 12 years ago63 messageshackers
Jump to latest
#1Thom Brown
thom@linux.com

Hi all,

Application to Google Summer of Code 2014 can be made as of next
Monday (3rd Feb), and then there will be a 12 day window in which to
submit an application.

I'd like to gauge interest from both mentors and students as to
whether we'll want to do this.

And I'd be fine with being admin again this year, unless there's
anyone else who would like to take up the mantle?

Who would be up for mentoring this year? And are there any project
ideas folk would like to suggest?

Thanks

Thom

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

#2Atri Sharma
atri.jiit@gmail.com
In reply to: Thom Brown (#1)
Re: [pgsql-advocacy] GSoC 2014 - mentors, students and admins

On Tue, Jan 28, 2014 at 11:04 PM, Thom Brown <thom@linux.com> wrote:

Hi all,

Application to Google Summer of Code 2014 can be made as of next
Monday (3rd Feb), and then there will be a 12 day window in which to
submit an application.

I'd like to gauge interest from both mentors and students as to
whether we'll want to do this.

And I'd be fine with being admin again this year, unless there's
anyone else who would like to take up the mantle?

Who would be up for mentoring this year? And are there any project
ideas folk would like to suggest?

Hi,

I would like to bring up the addition to MADLIB algorithms again this year.

Also, some work on the foreign table constraints could be helpful.

Regards,

Atri

--
Regards,

Atri
*l'apprenant*

#3Atri Sharma
atri.jiit@gmail.com
In reply to: Atri Sharma (#2)
Re: GSoC 2014 - mentors, students and admins

On Tue, Jan 28, 2014 at 11:16 PM, Atri Sharma <atri.jiit@gmail.com> wrote:

On Tue, Jan 28, 2014 at 11:04 PM, Thom Brown <thom@linux.com> wrote:

Hi all,

Application to Google Summer of Code 2014 can be made as of next
Monday (3rd Feb), and then there will be a 12 day window in which to
submit an application.

I'd like to gauge interest from both mentors and students as to
whether we'll want to do this.

And I'd be fine with being admin again this year, unless there's
anyone else who would like to take up the mantle?

Who would be up for mentoring this year? And are there any project
ideas folk would like to suggest?

Hi,

I would like to bring up the addition to MADLIB algorithms again this year.

Also, some work on the foreign table constraints could be helpful.

Hi,

Also, can we consider a project in an extension to be a project in GSoC
2014 as GSoC 2014 under PostgreSQL?

I was thinking of having some support for writable FDW in JDBC_FDW, if
possible.

Regards,

Atri
--
Regards,

Atri
*l'apprenant*

#4Josh Berkus
josh@agliodbs.com
In reply to: Thom Brown (#1)
Re: [pgsql-advocacy] GSoC 2014 - mentors, students and admins

On 01/28/2014 09:46 AM, Atri Sharma wrote:

I would like to bring up the addition to MADLIB algorithms again this year.

Also, some work on the foreign table constraints could be helpful.

We can only take MADLIB this year if we have confirmed mentors who are
MADLIB committers before the end of the application period (Feb 15). We
can't have a repeat of last year.

--
Josh Berkus
PostgreSQL Experts Inc.
http://pgexperts.com

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

#5Stephen Frost
sfrost@snowman.net
In reply to: Thom Brown (#1)
Re: GSoC 2014 - mentors, students and admins

Thom,

* Thom Brown (thom@linux.com) wrote:

Application to Google Summer of Code 2014 can be made as of next
Monday (3rd Feb), and then there will be a 12 day window in which to
submit an application.

This is just for PG to be a participating organization, right? There's
a while before mentors and students get invovled, as I understand it.

I'd like to gauge interest from both mentors and students as to
whether we'll want to do this.

Yes.

And I'd be fine with being admin again this year, unless there's
anyone else who would like to take up the mantle?

Having you do it works for me. :)

Who would be up for mentoring this year? And are there any project
ideas folk would like to suggest?

I'm interested in mentoring and, unlike previous years, I've been
collecting a personal list of things that I'd like to see worked on for
PG which could be GSoC projects and will provide such in the next few
days to this list (unless there's a different list that people want such
posted to..?).

Thanks,

Stephen

#6Maxence Ahlouche
maxence.ahlouche@gmail.com
In reply to: Josh Berkus (#4)
Re: [pgsql-advocacy] GSoC 2014 - mentors, students and admins

Hi all,

I'd very interesting in taking part in the GSoC with PostgreSQL, as a
student.
Being quite busy at the moment (exam time), I haven't had time to think of
a subject yet, even though I could see some topics I found interesting.

2014-01-28 Josh Berkus <josh@agliodbs.com>

On 01/28/2014 09:46 AM, Atri Sharma wrote:

I would like to bring up the addition to MADLIB algorithms again this

year.
We can only take MADLIB this year if we have confirmed mentors who are
MADLIB committers before the end of the application period (Feb 15). We
can't have a repeat of last year.

Indeed, I've been unlucky last year when I tried to apply to a subject with
Madlib, mostly due to their lack of reactivity. Even though their subjects
interest me, I don't intend to try my luck again.

Atri Sharma said:

Also, some work on the foreign table constraints could be helpful.

What kind of work do you have in mind?

Stephen Frost said:

I'm interested in mentoring and, unlike previous years, I've been
collecting a personal list of things that I'd like to see worked on for
PG which could be GSoC projects and will provide such in the next few
days to this list (unless there's a different list that people want such
posted to..?).

IMO, the best place would be the wiki page for GSoC (
http://wiki.postgresql.org/wiki/GSoC_2014), it would avoid interested
students (including me :) ) having to look for possible subjects in lots of
different places.

Regards,
Maxence
--
Maxence Ahlouche
06 06 66 97 00

#7Thom Brown
thom@linux.com
In reply to: Stephen Frost (#5)
Re: GSoC 2014 - mentors, students and admins

On 28 January 2014 19:43, Stephen Frost <sfrost@snowman.net> wrote:

Thom,

* Thom Brown (thom@linux.com) wrote:

Application to Google Summer of Code 2014 can be made as of next
Monday (3rd Feb), and then there will be a 12 day window in which to
submit an application.

This is just for PG to be a participating organization, right? There's
a while before mentors and students get invovled, as I understand it.

Yes, correct. Students and mentors don't need to be signed up until April.

Who would be up for mentoring this year? And are there any project
ideas folk would like to suggest?

I'm interested in mentoring and, unlike previous years, I've been
collecting a personal list of things that I'd like to see worked on for
PG which could be GSoC projects and will provide such in the next few
days to this list (unless there's a different list that people want such
posted to..?).

That's great. I don't see any problem with posting suggestions here,
although I'd suggest refraining from going in-depth as that can come
later. If there's enough interest and agreement, we'll go ahead and
apply.

Thom

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

#8Heikki Linnakangas
heikki.linnakangas@enterprisedb.com
In reply to: Thom Brown (#1)
Re: [HACKERS] GSoC 2014 - mentors, students and admins

On 01/28/2014 07:34 PM, Thom Brown wrote:

And I'd be fine with being admin again this year, unless there's
anyone else who would like to take up the mantle?

Please do, thanks!

Who would be up for mentoring this year?

I can mentor.

- Heikki

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

#9David Fetter
david@fetter.org
In reply to: Thom Brown (#1)
Re: GSoC 2014 - mentors, students and admins

On Tue, Jan 28, 2014 at 05:34:21PM +0000, Thom Brown wrote:

Hi all,

Application to Google Summer of Code 2014 can be made as of next
Monday (3rd Feb), and then there will be a 12 day window in which to
submit an application.

I'd like to gauge interest from both mentors and students as to
whether we'll want to do this.

And I'd be fine with being admin again this year, unless there's
anyone else who would like to take up the mantle?

Thanks for your hard work administering last year, and thanks even
more for taking this on in light of that experience :)

Who would be up for mentoring this year? And are there any project
ideas folk would like to suggest?

I'd be delighted to mentor.

Cheers,
David.
--
David Fetter <david@fetter.org> http://fetter.org/
Phone: +1 415 235 3778 AIM: dfetter666 Yahoo!: dfetter
Skype: davidfetter XMPP: david.fetter@gmail.com
iCal: webcal://www.tripit.com/feed/ical/people/david74/tripit.ics

Remember to vote!
Consider donating to Postgres: http://www.postgresql.org/about/donate

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

#10Alexander Korotkov
aekorotkov@gmail.com
In reply to: Thom Brown (#1)
Re: [HACKERS] GSoC 2014 - mentors, students and admins

Hi!

On Tue, Jan 28, 2014 at 9:34 PM, Thom Brown <thom@linux.com> wrote:

And I'd be fine with being admin again this year, unless there's
anyone else who would like to take up the mantle?

Thanks for your work. I would like to see you as admin this year again.

Who would be up for mentoring this year? And are there any project

ideas folk would like to suggest?

I would like to be mentor.

------
With best regards,
Alexander Korotkov.

#11Andreas 'ads' Scherbaum
adsmail@wars-nicht.de
In reply to: Atri Sharma (#2)
Re: GSoC 2014 - mentors, students and admins

Hi,

On 01/28/2014 06:46 PM, Atri Sharma wrote:

On Tue, Jan 28, 2014 at 11:04 PM, Thom Brown <thom@linux.com
<mailto:thom@linux.com>> wrote:

Hi all,

Application to Google Summer of Code 2014 can be made as of next
Monday (3rd Feb), and then there will be a 12 day window in which to
submit an application.

I'd like to gauge interest from both mentors and students as to
whether we'll want to do this.

And I'd be fine with being admin again this year, unless there's
anyone else who would like to take up the mantle?

Who would be up for mentoring this year? And are there any project
ideas folk would like to suggest?

I would like to bring up the addition to MADLIB algorithms again this year.

I've spoken with the MADlib team at goivotal and they are ok to support
this proposal. Therefore I offer to mentor this.

Regards,

--
Andreas 'ads' Scherbaum
German PostgreSQL User Group
European PostgreSQL User Group - Board of Directors
Volunteer Regional Contact, Germany - PostgreSQL Project

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

#12Atri Sharma
atri.jiit@gmail.com
In reply to: Andreas 'ads' Scherbaum (#11)
Re: [pgsql-advocacy] GSoC 2014 - mentors, students and admins

Awesome. I can be an assistant mentor for this one is possible or I could
mentor some other project.

On Tuesday, February 25, 2014, Andreas 'ads' Scherbaum <
adsmail@wars-nicht.de> wrote:

Hi,

On 01/28/2014 06:46 PM, Atri Sharma wrote:

On Tue, Jan 28, 2014 at 11:04 PM, Thom Brown <thom@linux.com
<mailto:thom@linux.com>> wrote:

Hi all,

Application to Google Summer of Code 2014 can be made as of next
Monday (3rd Feb), and then there will be a 12 day window in which to
submit an application.

I'd like to gauge interest from both mentors and students as to
whether we'll want to do this.

And I'd be fine with being admin again this year, unless there's
anyone else who would like to take up the mantle?

Who would be up for mentoring this year? And are there any project
ideas folk would like to suggest?

I would like to bring up the addition to MADLIB algorithms again this
year.

I've spoken with the MADlib team at goivotal and they are ok to support
this proposal. Therefore I offer to mentor this.

Regards,

--
Andreas 'ads' Scherbaum
German PostgreSQL User Group
European PostgreSQL User Group - Board of Directors
Volunteer Regional Contact, Germany - PostgreSQL Project

--
Regards,

Atri
*l'apprenant*

#13Thom Brown
thom@linux.com
In reply to: Andreas 'ads' Scherbaum (#11)
Re: GSoC 2014 - mentors, students and admins

On 25 February 2014 13:28, Andreas 'ads' Scherbaum <adsmail@wars-nicht.de>wrote:

Hi,

On 01/28/2014 06:46 PM, Atri Sharma wrote:

On Tue, Jan 28, 2014 at 11:04 PM, Thom Brown <thom@linux.com
<mailto:thom@linux.com>> wrote:

Hi all,

Application to Google Summer of Code 2014 can be made as of next
Monday (3rd Feb), and then there will be a 12 day window in which to
submit an application.

I'd like to gauge interest from both mentors and students as to
whether we'll want to do this.

And I'd be fine with being admin again this year, unless there's
anyone else who would like to take up the mantle?

Who would be up for mentoring this year? And are there any project
ideas folk would like to suggest?

I would like to bring up the addition to MADLIB algorithms again this
year.

I've spoken with the MADlib team at goivotal and they are ok to support
this proposal. Therefore I offer to mentor this.

Are there any more prospective mentors? We'll want some folk to act as
back-up mentors too to ensure projects can still be completed should any
mentor become unavailable.

--
Thom

#14David Fetter
david@fetter.org
In reply to: Thom Brown (#13)
Re: [pgsql-advocacy] GSoC 2014 - mentors, students and admins

On Thu, Feb 27, 2014 at 07:54:13PM +0000, Thom Brown wrote:

On 25 February 2014 13:28, Andreas 'ads' Scherbaum <adsmail@wars-nicht.de>wrote:

I've spoken with the MADlib team at goivotal and they are ok to
support this proposal. Therefore I offer to mentor this.

Are there any more prospective mentors? We'll want some folk to act
as back-up mentors too to ensure projects can still be completed
should any mentor become unavailable.

For MADlib, no. Are you asking for mentors in general?

Cheers,
David.
--
David Fetter <david@fetter.org> http://fetter.org/
Phone: +1 415 235 3778 AIM: dfetter666 Yahoo!: dfetter
Skype: davidfetter XMPP: david.fetter@gmail.com
iCal: webcal://www.tripit.com/feed/ical/people/david74/tripit.ics

Remember to vote!
Consider donating to Postgres: http://www.postgresql.org/about/donate

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

#15Thom Brown
thom@linux.com
In reply to: David Fetter (#14)
Re: [HACKERS] GSoC 2014 - mentors, students and admins

On 27 February 2014 21:08, David Fetter <david@fetter.org> wrote:

On Thu, Feb 27, 2014 at 07:54:13PM +0000, Thom Brown wrote:

On 25 February 2014 13:28, Andreas 'ads' Scherbaum <

adsmail@wars-nicht.de>wrote:

I've spoken with the MADlib team at goivotal and they are ok to
support this proposal. Therefore I offer to mentor this.

Are there any more prospective mentors? We'll want some folk to act
as back-up mentors too to ensure projects can still be completed
should any mentor become unavailable.

For MADlib, no. Are you asking for mentors in general?

Ah yes, I should clarify. Yes, mentors in general.

--
Thom

#16Bruce Momjian
bruce@momjian.us
In reply to: Thom Brown (#1)
Re: GSoC 2014 - mentors, students and admins

On Tue, Jan 28, 2014 at 5:34 PM, Thom Brown <thom@linux.com> wrote:

Who would be up for mentoring this year? And are there any project
ideas folk would like to suggest?

I mentored in the past and felt I didn't do a very good job because I
didn't really understand the project the student was working on.

There's precisely one project that I feel I would be competent to
mentor at this point. Making hash indexes WAL recoverable. This is
something that's easy to define the scope of and easy to determine if
the student is on track and easy to measure when finished. It's
something where as far as I can tell all the mentor work will be
purely technical advice.

Also it's something the project really really needs and is perfectly
sized for a GSOC project IMHO. Also it's a great project for a student
who might be interested in working on Postgres in the future since it
requires learning all our idiosyncratic build and source conventions
but doesn't require huge or controversial architectural changes.

I fear a number of items in the Wiki seem unrealistically large
projects for GSOC IMNSHO.

--
greg

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

#17Karol Trzcionka
karlikt@gmail.com
In reply to: Thom Brown (#15)
Re: [HACKERS] GSoC 2014 - mentors, students and admins

W dniu 27.02.2014 22:25, Thom Brown pisze:

On 27 February 2014 21:08, David Fetter <david@fetter.org
<mailto:david@fetter.org>> wrote:

For MADlib, no. Are you asking for mentors in general?

Ah yes, I should clarify. Yes, mentors in general.

In general I can help but I'm not sure if I'm not too fresh in pgsql ;)
However after GSOC as student I can try "the another side".
Regards,
Karol

#18Tan Tran
tankimtran@gmail.com
In reply to: Bruce Momjian (#16)
Re: GSoC 2014 - mentors, students and admins

Hi Greg, pgsql-advocacy, and pgsql-hackers,

I'm interested in doing my GSoC project on this idea. I'm new to indexing and WAL, which I haven't encountered in my classes, but it sounds interesting and valuable to Postgresql. So here's my draft proposal. Do you mind giving your opinion and corrections? With your help I'll add some technical detail to my plans.

Thanks,
Tan Tran

Introduction
In write-ahead logging (WAL), all modifications to a database are written to a write-ahead log before being flushed to disk at periodic checkpoints. This method saves I/O operations, enables a continuous backup, and, in the case of database failure, guarantees data integrity up until the last saved checkpoint. In Postgresql’s implementation, transactions are written to XLog, which is divided into 16MB files (“segments”) that together comprise a complete history of transactions. Transactions are continually appended to the latest segment, while checkpointing continually archives segments up until the last checkpoint. Internally, a suite of XLog structures and functions interfaces with the various resource managers so they can log a sufficient amount of data to restore data (“redo”) in case of failure.
Another Postgresql feature is the creation of indexes on a invariant custom field; for example, on the LastName of a Person even though the primary key is ID. These custom indexes speed up row lookup. Postgres currently supports four index types: B-tree, GiST, and GIN, and hash. Indexes on the former three are WAL-recoverable, but hashing is not.

2. Proposal
As a GSoC student, I will implement WAL recovery of hash indexes using the other index types’ WAL code as a guide. Roughly, I will:
- Devise a way to store and retrieve hashing data within the XLog data structures.
- In the existing skeleton for hash_redo(XLogRecPtr lsn, XLogRecord *record) in hash.c, branch to code for the various redo operations: creating an index, inserting into an index, deleting an index, and page operations (split, delete, update?).
- Code each branch by drawing on examples from btree_redo, gin_redo, and gist_redo, the existing XLog code of the other index types.

Benefits
Hash index searching is O(1), which is asymptotically faster than the O(n lg n) searching of a B-tree, and does not require custom indexing functions like GIN and GIST inherently do. Therefore it is desirable for rows that will only be retrieved on an equality or inequality relation. However, two things currently stand in the way of its popular use. From the Postgresql documentation,
“Hash index operations are not presently WAL-logged, so hash indexes might need to be rebuilt with REINDEX after a database crash if there were unwritten changes. Also, changes to hash indexes are not replicated over streaming or file-based replication after the initial base backup, so they give wrong answers to queries that subsequently use them. For these reasons, hash index use is presently discouraged.”
My project would solve the first problem, after which I would like to stay on and fix the second.

To be written: Quantifiable Results, Schedule, Completeness Criteria, Bio

On Feb 28, 2014, at 6:21 AM, Greg Stark <stark@mit.edu> wrote:

Show quoted text

On Tue, Jan 28, 2014 at 5:34 PM, Thom Brown <thom@linux.com> wrote:

Who would be up for mentoring this year? And are there any project
ideas folk would like to suggest?

I mentored in the past and felt I didn't do a very good job because I
didn't really understand the project the student was working on.

There's precisely one project that I feel I would be competent to
mentor at this point. Making hash indexes WAL recoverable. This is
something that's easy to define the scope of and easy to determine if
the student is on track and easy to measure when finished. It's
something where as far as I can tell all the mentor work will be
purely technical advice.

Also it's something the project really really needs and is perfectly
sized for a GSOC project IMHO. Also it's a great project for a student
who might be interested in working on Postgres in the future since it
requires learning all our idiosyncratic build and source conventions
but doesn't require huge or controversial architectural changes.

I fear a number of items in the Wiki seem unrealistically large
projects for GSOC IMNSHO.

--
greg

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

#19Tan Tran
tankimtran@gmail.com
In reply to: Karol Trzcionka (#17)
Re: [pgsql-advocacy] GSoC 2014 - mentors, students and admins

Earlier I posted an email to this thread that I realize "hijacked" the discussion. Please continue replying to here instead.

On Feb 28, 2014, at 6:59 AM, Karol Trzcionka <karlikt@gmail.com> wrote:

Show quoted text

W dniu 27.02.2014 22:25, Thom Brown pisze:

On 27 February 2014 21:08, David Fetter <david@fetter.org> wrote:
For MADlib, no. Are you asking for mentors in general?

Ah yes, I should clarify. Yes, mentors in general.

In general I can help but I'm not sure if I'm not too fresh in pgsql ;) However after GSOC as student I can try "the another side".
Regards,
Karol

#20Tan Tran
tankimtran@gmail.com
In reply to: Tan Tran (#18)
GSoC on WAL-logging hash indexes

Hi all,

Earlier I posted this in the wrong thread. Please excuse the double posting.

Tan Tran

Begin forwarded message:

Show quoted text

From: Tan Tran <tankimtran@gmail.com>
Subject: Re: [HACKERS] GSoC 2014 - mentors, students and admins
Date: March 2, 2014 at 5:03:14 AM PST
To: Greg Stark <stark@mit.edu>
Cc: pgsql-advocacy <pgsql-advocacy@postgresql.org>, PostgreSQL-development <pgsql-hackers@postgresql.org>

Hi Greg, pgsql-advocacy, and pgsql-hackers,

I'm interested in doing my GSoC project on this idea. I'm new to indexing and WAL, which I haven't encountered in my classes, but it sounds interesting and valuable to Postgresql. So here's my draft proposal. Do you mind giving your opinion and corrections? With your help I'll add some technical detail to my plans.

Thanks,
Tan Tran

Introduction
In write-ahead logging (WAL), all modifications to a database are written to a write-ahead log before being flushed to disk at periodic checkpoints. This method saves I/O operations, enables a continuous backup, and, in the case of database failure, guarantees data integrity up until the last saved checkpoint. In Postgresql’s implementation, transactions are written to XLog, which is divided into 16MB files (“segments”) that together comprise a complete history of transactions. Transactions are continually appended to the latest segment, while checkpointing continually archives segments up until the last checkpoint. Internally, a suite of XLog structures and functions interfaces with the various resource managers so they can log a sufficient amount of data to restore data (“redo”) in case of failure.
Another Postgresql feature is the creation of indexes on a invariant custom field; for example, on the LastName of a Person even though the primary key is ID. These custom indexes speed up row lookup. Postgres currently supports four index types: B-tree, GiST, and GIN, and hash. Indexes on the former three are WAL-recoverable, but hashing is not.

2. Proposal
As a GSoC student, I will implement WAL recovery of hash indexes using the other index types’ WAL code as a guide. Roughly, I will:
- Devise a way to store and retrieve hashing data within the XLog data structures.
- In the existing skeleton for hash_redo(XLogRecPtr lsn, XLogRecord *record) in hash.c, branch to code for the various redo operations: creating an index, inserting into an index, deleting an index, and page operations (split, delete, update?).
- Code each branch by drawing on examples from btree_redo, gin_redo, and gist_redo, the existing XLog code of the other index types.

Benefits
Hash index searching is O(1), which is asymptotically faster than the O(n lg n) searching of a B-tree, and does not require custom indexing functions like GIN and GIST inherently do. Therefore it is desirable for rows that will only be retrieved on an equality or inequality relation. However, two things currently stand in the way of its popular use. From the Postgresql documentation,
“Hash index operations are not presently WAL-logged, so hash indexes might need to be rebuilt with REINDEX after a database crash if there were unwritten changes. Also, changes to hash indexes are not replicated over streaming or file-based replication after the initial base backup, so they give wrong answers to queries that subsequently use them. For these reasons, hash index use is presently discouraged.”
My project would solve the first problem, after which I would like to stay on and fix the second.

To be written: Quantifiable Results, Schedule, Completeness Criteria, Bio

On Feb 28, 2014, at 6:21 AM, Greg Stark <stark@mit.edu> wrote:

On Tue, Jan 28, 2014 at 5:34 PM, Thom Brown <thom@linux.com> wrote:

Who would be up for mentoring this year? And are there any project
ideas folk would like to suggest?

I mentored in the past and felt I didn't do a very good job because I
didn't really understand the project the student was working on.

There's precisely one project that I feel I would be competent to
mentor at this point. Making hash indexes WAL recoverable. This is
something that's easy to define the scope of and easy to determine if
the student is on track and easy to measure when finished. It's
something where as far as I can tell all the mentor work will be
purely technical advice.

Also it's something the project really really needs and is perfectly
sized for a GSOC project IMHO. Also it's a great project for a student
who might be interested in working on Postgres in the future since it
requires learning all our idiosyncratic build and source conventions
but doesn't require huge or controversial architectural changes.

I fear a number of items in the Wiki seem unrealistically large
projects for GSOC IMNSHO.

--
greg

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

#21Robert Haas
robertmhaas@gmail.com
In reply to: Tan Tran (#20)
#22Tan Tran
tankimtran@gmail.com
In reply to: Robert Haas (#21)
#23Anastasia Lubennikova
a.lubennikova@postgrespro.ru
In reply to: Thom Brown (#1)
#24Jeff Janes
jeff.janes@gmail.com
In reply to: Tan Tran (#22)
#25Bruce Momjian
bruce@momjian.us
In reply to: Robert Haas (#21)
#26Heikki Linnakangas
heikki.linnakangas@enterprisedb.com
In reply to: Bruce Momjian (#25)
#27Robert Haas
robertmhaas@gmail.com
In reply to: Heikki Linnakangas (#26)
#28Jeff Janes
jeff.janes@gmail.com
In reply to: Robert Haas (#27)
#29Robert Haas
robertmhaas@gmail.com
In reply to: Jeff Janes (#28)
#30Bruce Momjian
bruce@momjian.us
In reply to: Robert Haas (#29)
#31Heikki Linnakangas
heikki.linnakangas@enterprisedb.com
In reply to: Robert Haas (#27)
#32Robert Haas
robertmhaas@gmail.com
In reply to: Bruce Momjian (#30)
#33Robert Haas
robertmhaas@gmail.com
In reply to: Heikki Linnakangas (#31)
#34Heikki Linnakangas
heikki.linnakangas@enterprisedb.com
In reply to: Robert Haas (#33)
In reply to: Robert Haas (#29)
#36Heikki Linnakangas
heikki.linnakangas@enterprisedb.com
In reply to: Robert Haas (#33)
#37Thom Brown
thom@linux.com
In reply to: Thom Brown (#1)
#38Stephen Frost
sfrost@snowman.net
In reply to: Stephen Frost (#5)
#39Fabrízio de Royes Mello
fabriziomello@gmail.com
In reply to: Stephen Frost (#38)
#40Thom Brown
thom@linux.com
In reply to: Thom Brown (#1)
In reply to: Robert Haas (#21)
In reply to: Peter Geoghegan (#41)
In reply to: Kenneth Marshall (#42)
#44Robert Haas
robertmhaas@gmail.com
In reply to: Peter Geoghegan (#43)
#45Josh Berkus
josh@agliodbs.com
In reply to: Tan Tran (#18)
#46Tom Lane
tgl@sss.pgh.pa.us
In reply to: Robert Haas (#44)
In reply to: Robert Haas (#44)
#48Jeff Janes
jeff.janes@gmail.com
In reply to: Peter Geoghegan (#41)
In reply to: Tom Lane (#46)
#50Jeff Janes
jeff.janes@gmail.com
In reply to: Peter Geoghegan (#47)
#51Andres Freund
andres@anarazel.de
In reply to: Jeff Janes (#50)
#52Robert Haas
robertmhaas@gmail.com
In reply to: Peter Geoghegan (#47)
In reply to: Jeff Janes (#48)
#54Bruce Momjian
bruce@momjian.us
In reply to: Peter Geoghegan (#53)
#55Stephen Frost
sfrost@snowman.net
In reply to: Bruce Momjian (#54)
#56Jeff Janes
jeff.janes@gmail.com
In reply to: Peter Geoghegan (#53)
#57Alvaro Herrera
alvherre@2ndquadrant.com
In reply to: Stephen Frost (#55)
#58Jeff Janes
jeff.janes@gmail.com
In reply to: Bruce Momjian (#54)
#59Darren Duncan
darren@darrenduncan.net
In reply to: Peter Geoghegan (#41)
#60Tom Lane
tgl@sss.pgh.pa.us
In reply to: Bruce Momjian (#54)
#61Vik Fearing
vik@postgresfriends.org
In reply to: Tom Lane (#60)
#62Michael Paquier
michael@paquier.xyz
In reply to: Vik Fearing (#61)
#63Vik Fearing
vik@postgresfriends.org
In reply to: Michael Paquier (#62)