Re: Call for Google Summer of Code mentors, admins - Mailing list pgsql-hackers

From Fabrízio de Royes Mello
Subject Re: Call for Google Summer of Code mentors, admins
Date
Msg-id CAFcNs+oY3jujp1+gXQ7rr6V+2bJhQTt3PQtyrLwO0AMmA3gCWA@mail.gmail.com
Whole thread Raw
In response to Re: Call for Google Summer of Code mentors, admins  (Heikki Linnakangas <hlinnakangas@vmware.com>)
List pgsql-hackers

On Tue, Feb 19, 2013 at 5:43 PM, Heikki Linnakangas <hlinnakangas@vmware.com> wrote:
On 19.02.2013 20:07, Fabrízio de Royes Mello wrote:
I would like to propose implement a way to track creation times to database
objects. This was discussed before in this thread [1].

This was discussed before in this thread [1] but we don't reach a consensus
of what we'll do, so I propose we discuss any more about it and I can
implement it in GSOC2013, if my proposal will be accepted.

I don't think that's a good GSoC project. There's no consensus on what to do, if anything, so 95% of the work is going to arguing over what we want, and 5% coding. I'd suggest finding something more well-defined.


You all right about we don't have no consensus on what to do, but maybe this can be a opportunity to we do that.

I know a lot of people (friends, customers, users, ...) who would love to have this feature in future versions of PostgreSQL.

Anyway there is another well defined feature which you recommend to a good GSoC project?

Best regards,

--
Fabrízio de Royes Mello
Consultoria/Coaching PostgreSQL
>> Blog sobre TI: http://fabriziomello.blogspot.com
>> Perfil Linkedin: http://br.linkedin.com/in/fabriziomello
>> Twitter: http://twitter.com/fabriziomello

pgsql-hackers by date:

Previous
From: Kevin Grittner
Date:
Subject: Re: Materialized views WIP patch
Next
From: Ian Lawrence Barwick
Date:
Subject: Re: [DOCS] Contrib module "xml2" status