On 11/20/2016 07:20 AM, Job wrote:
Hi Adrian,
Thank you for your fast reply!
FYI, Postgres 8.4 is over two years past EOL.
Yes, i am aware; we will migrate next year but for application compatibility reason we have at the moment to the remain here..
What are the steps in the load/delete cycle?
We need to load, with pg_bulkload, log datas for reporting.
We load every hours about one million of row and twice a day we generated aggregated report.
Then we delete old rows (we cannot use truncate because we only delere rows older than 24 hours).
I think, but i can be wrong, that pg_bulkload do not reuse free space marked previously by the delete..
Can you be more specific.
In other words show the actual commands you use?
Also how are you defining free space, space the OS sees or space
Postgres sees?
How are you determining the free space?
Only vacuum full empty free space, but tablea became locked.
VACUUM full returns space to the OS if that is what you mean?
Thank you
Francesco
--
Adrian Klaver
adrian.klaver@xxxxxxxxxxx
--
Sent via pgsql-general mailing list (pgsql-general@xxxxxxxxxxxxxx)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general
