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 <[email protected]>
To: Rakesh Kumar <[email protected]>; "[email protected]"
<[email protected]>
Sent: Monday, June 20, 2016 5:39 AM
Subject: R: [GENERAL] Vacuum full: alternatives?
#yiv6783361115 #yiv6783361115 --P
{MARGIN-BOTTOM:0px;MARGIN-TOP:0px;}#yiv6783361115 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: [email protected]
[[email protected]] per conto di Rakesh Kumar
[[email protected]]
Inviato: lunedì 20 giugno 2016 11.34
A: [email protected]
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 <[email protected]>
To: "[email protected]" <[email protected]>
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 ([email protected])
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general
