| From: | Job <Job(at)colliniconsulting(dot)it> |
|---|---|
| To: | Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com>, "pgsql-general(at)postgresql(dot)org" <pgsql-general(at)postgresql(dot)org> |
| Subject: | R: Autovacuum and frequent pg_bulkload |
| Date: | 2016-11-20 15:20:31 |
| Message-ID: | 88EF58F000EC4B4684700C2AA3A73D7A08054EAEBAE2@W2008DC01.ColliniConsulting.lan |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
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..
Only vacuum full empty free space, but tablea became locked.
Thank you
Francesco
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Adrian Klaver | 2016-11-20 16:03:57 | Re: R: Autovacuum and frequent pg_bulkload |
| Previous Message | Adrian Klaver | 2016-11-20 14:50:59 | Re: Autovacuum and frequent pg_bulkload |