Big table and partition - Mailing list pgsql-admin

From Rajesh Kumar
Subject Big table and partition
Date
Msg-id CAJk5AtYv5x9_j9HtRtt_7JE-p-Fs2sA_kb2u4fbNcwwsqNVqMQ@mail.gmail.com
Whole thread Raw
Responses Re: Big table and partition
Re: Big table and partition
List pgsql-admin
Hi 

In my env, I have a table 30GB where data is getting inserted directly whenever the new block is created in block chain...

Sometimes, there is a query running to check whether the recent block is created ?

I have been asked to do partition, i said manager since we are not at all using the past data, partition is not required. Instead we can stop the sync (downtime not required), change the name of table , create a new table with same structure with original name and keep only tis month data. Then sync the blockchain so that new data will come to newly created table and old data will be there simply as a storage as we r not selecting any query from old data...

Note: on a longer run, data will keep on coming in whenever new block is created.

Is that right ? Any suggestions ? Better options ?



pgsql-admin by date:

Previous
From: Jean-Christophe Boggio
Date:
Subject: Re: One PG process eating more than 40GB of RAM and getting killed by OOM
Next
From: Ron
Date:
Subject: Re: Big table and partition