Re: Table size - optimization - Mailing list pgsql-admin

From Marius
Subject Re: Table size - optimization
Date
Msg-id 566ea6cb.46b71c0a.17f65.5010@mx.google.com
Whole thread Raw
In response to Table size - optimization  ("drum.lucas@gmail.com" <drum.lucas@gmail.com>)
List pgsql-admin
You could simply rename old table, create new one and all in same transaction. No data move required.

From: drum.lucas@gmail.com
Sent: 2015.12.14 06:37
To: pgsql-admin@postgresql.org
Subject: [ADMIN] Table size - optimization

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

pgsql-admin by date:

Previous
From: Shreeyansh Dba
Date:
Subject: Re: Oracle to Postgres Migration - Duplicate Key Issue
Next
From: Gustav Karlsson
Date:
Subject: Proper way to restore from a basebackup without the WAL-files?