On Mon, Jun 20, 2016 at 8:29 AM, Rakesh Kumar <rakeshkumar46...@gmail.com> wrote:
> But then autovaccum avoids this. Granted it won't give back free space to > OS, but it won't let it grow too (or am I missing something). > > > ------------------------------ > *From:* Job <j...@colliniconsulting.it> > *To:* Rakesh Kumar <rakeshkumar46...@gmail.com>; " > pgsql-general@postgresql.org" <pgsql-general@postgresql.org> > *Sent:* Monday, June 20, 2016 5:39 AM > *Subject:* R: [GENERAL] Vacuum full: alternatives? > > Hi Rakesh, > > if i do not free disk space, after some days disk can become full. > Everyday we have a lot of pg_bulkload and delete. > > Thank you! > Francesco > > ------------------------------ > *Da:* pgsql-general-ow...@postgresql.org [ > pgsql-general-ow...@postgresql.org] per conto di Rakesh Kumar [ > rakeshkumar46...@gmail.com] > *Inviato:* lunedì 20 giugno 2016 11.34 > *A:* pgsql-general@postgresql.org > *Oggetto:* Re: [GENERAL] Vacuum full: alternatives? > > Any reason why you need the space back? What is wrong with space remaining > constant at 4GB. > > > ------------------------------ > *From:* Job <j...@colliniconsulting.it> > *To:* "pgsql-general@postgresql.org" <pgsql-general@postgresql.org> > *Sent:* Monday, June 20, 2016 5:18 AM > *Subject:* [GENERAL] Vacuum full: alternatives? > > Hello, > > we have a table with an heavy traffic of pg_bulkload and delete of records. > The size pass, in only one day, for example for 1Gb to 4Gb and then 1Gb > back. > > We have important problems on size and the only way to gain free space is > issueing a vacuum full <table>. > But the operation is very slow, sometimes 2/4 hours, and table is not > available for services as it is locked. > > We do not delete everything at one (in this case the truncate woudl > resolve the problem). > > The autovacuum is not able (same for normal vacuum) to free the spaces. > > Are there some suggestions or another way to manage this? > > Thank you! > Francesco > > -- > Sent via pgsql-general mailing list (pgsql-general@postgresql.org) > To make changes to your subscription: > http://www.postgresql.org/mailpref/pgsql-general > > > > > but it won't let it grow too (or am I missing something). Yes, you are missing something. By partioning and {Vacuum Full only the table with data no longer needed}, the rest of the data remains available to the users AND space is reclaimed by the O/S, so it's the best of both worlds. -- *Melvin Davidson* I reserve the right to fantasize. Whether or not you wish to share my fantasy is entirely up to you.
