Table size - optimization

From: "drum(dot)lucas(at)gmail(dot)com" <drum(dot)lucas(at)gmail(dot)com>
To: pgsql-admin(at)postgresql(dot)org
Subject: Table size - optimization
Date: 2015-12-14 04:35:40
Message-ID: CAE_gQfXyu0R=6ThVfsHNYhMda-zUv9m7xxo=WCYxWyyzi=qgzQ@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-admin

Feedlog is a central area where theres been a lot of data dumped together
and the beast has grown.

Whats a better way to design the db table(s) for feedlog so we can get a
very large performance gain.

Is there a way we can create a feedlog-history table or yearly tables eg
feedlog-2014 and move old data out of the original table so its a kean fast
table?

What code would need to change to deal with that?

*Some data :*

Size: 8 GB

relname | relkind | reltuples | relpages
-------------------+---------+-------------+----------
feedlog | r | 6.60508e+07 | 9974857

Thanks,
Lucas

Browse pgsql-admin by date

  From Date Subject
Next Message Shreeyansh Dba 2015-12-14 09:01:29 Re: Oracle to Postgres Migration - Duplicate Key Issue
Previous Message Matt Hempleman 2015-12-14 00:27:21 Oracle to Postgres Migration - Duplicate Key Issue