Re: GSOC PostgreSQL partitioning issue

On Thu, Apr 8, 2010 at 4:23 PM, Necati Batur <necatibatur(at)gmail(dot)com> wrote:
> In order to make a system change a student need to be more informed
> and experienced for the issue.Nonetheless,this step of work is
> actually not the phase of determining all the details,I
> guess.Otherwise,I would just do a few weeks of coding in summer to
> complete the project and I would be the person in charge in project
> management :)

Well, obviously there are going to be details that won't get worked
out until you really settle down to do the project. But I don't think
you've even really defined what exactly you would be working on.
Going through your deliverables one by one:

*The trigger based operations can be done automatically

What trigger-based operations are you talking about and how do you
plan to automate them?

*The stored procedures can help us to do some functionalities like
check constraint problem

What check constraint problem? PostgreSQL already has check
constraints. If you think they have a problem, say what it is.

*manual VACUUM or ANALYZE commands can be handled by using triggers
DBMS SQL can help to provide faster executions

We already have an autovacuum daemon that automates VACUUM and ANALYZE
commands and it works pretty well. Certainly, there's room for
improvement, but what do you think needs improving? What about the
current implementation do you not like and how do you propose to fix
it?

*Some more functionalities can be added to UPDATE operations to make
administrations easy

What administrations are currently difficult and what functionality do
you propose to add to simplify them?

...Robert