From: | Steve Crawford <scrawford(at)pinpointresearch(dot)com> |
---|---|
To: | Condor <condor(at)stz-bg(dot)com> |
Cc: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: Vacuum does not show in pg_stat_all_tables |
Date: | 2012-05-15 15:29:35 |
Message-ID: | 4FB2765F.90903@pinpointresearch.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On 05/15/2012 05:30 AM, Condor wrote:
> O
>
>
> I use vacuum full because I have huge tables that every night is
> deleted (truncated)
> and I want my space back.
Truncate does reclaim space. Bulk deletes do not. If you are doing bulk
deletes since you need to delete *almost* everything consider using
"cluster" to clean up. It is much faster and gives you new unbloated
indexes. You may find pg_reorg of interest as well.
> I did not use autovacuum because in past some times I lost
> data when is inserted. In past is happened once every month or two
> some record just missing.
>
>
This issue, perhaps?:
http://www.databasesoup.com/2012/03/postgres-update-release-data-loss-and.html
In which case the data was not actually lost but could be missing from
the index (with the obvious potential for resulting corruption). It has
been fixed in current versions.
Cheers,
Steve
From | Date | Subject | |
---|---|---|---|
Next Message | Mike Christensen | 2012-05-15 19:28:39 | Is there a way to avoid hard coding database connection info into views? |
Previous Message | Poul Møller Hansen | 2012-05-15 15:27:56 | Why are pg_restore taking that long ? |