| From: | Andy Colson <andy(at)squeakycode(dot)net> |
|---|---|
| To: | Stefan Keller <sfkeller(at)gmail(dot)com> |
| Cc: | pgsql-general List <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: Call for Google Summer of Code (GSoC) 2012: Project ideas? |
| Date: | 2012-03-08 20:01:13 |
| Message-ID: | 4F591009.5040009@squeakycode.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On 03/08/2012 01:40 PM, Stefan Keller wrote:
> Hi
>
> I do have a student who is interested in participating at the Google
> Summer of Code (GSoC) 2012
> 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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Aleksey Tsalolikhin | 2012-03-08 20:10:16 | Re: A 154 GB table swelled to 527 GB on the Slony slave. How to compact it? |
| Previous Message | Scott Marlowe | 2012-03-08 19:58:39 | Re: A 154 GB table swelled to 527 GB on the Slony slave. How to compact it? |