Re: Call for Google Summer of Code (GSoC) 2012: Project ideas? - Mailing list pgsql-general

From dennis jenkins
Subject Re: Call for Google Summer of Code (GSoC) 2012: Project ideas?
Date
Msg-id CAAEzAp80mROGLXOt81DM5LXJrG54bKKx25FdPN8NOKaB6xG9XQ@mail.gmail.com
Whole thread Raw
In response to Re: Call for Google Summer of Code (GSoC) 2012: Project ideas?  (Andy Colson <andy@squeakycode.net>)
List pgsql-general
>> Now I have the "burden" to look for a cool project... Any ideas?
>>
>> -Stefan
>>
>
> How about one of:
>
> 1) on disk page level compression (maybe with LZF or snappy) (maybe not page
> level, any level really)
>
> I know toast compresses, but I believe its only one row.  page level would
> compress better because there is more data, and it would also decrease the
> amount of IO, so it might speed up disk access.
>
> 2) better partitioning support.  Something much more automatic.
>
> 3) take a nice big table, have it inserted/updated a few times a second.
>  Then make "select * from bigtable where indexed_field = 'somevalue'; work
> 10 times faster than it does today.
>
>
> I think there is also a wish list on the wiki somewhere.
>
> -Andy
>

Ability to dynamically resize the shared-memory segment without taking
postgresql down :)

pgsql-general by date:

Previous
From: Aleksey Tsalolikhin
Date:
Subject: Re: A 154 GB table swelled to 527 GB on the Slony slave. How to compact it?
Next
From: Scott Marlowe
Date:
Subject: Re: A 154 GB table swelled to 527 GB on the Slony slave. How to compact it?