The vacuum tag has no wiki summary.
0
votes
1answer
30 views
“Truncate” or “Delete/Vacuum Full” for deleting some of the table rows
I have a db which has 223 tables and I have to delete some of the records from 10 of them, each has apprx. 1.5million records. Those tables are storing the temperatures every 7seconds. We have decided ...
2
votes
1answer
115 views
PostgreSQL 9.2: vacuum returning disk space to operating system
Vacuum usually does not return disk space to operating system, except some special cases.
From the docs:
The standard form of VACUUM removes dead row versions in tables and indexes and marks the ...
2
votes
1answer
49 views
What fillfactor for caching table?
I have heavily updated / accessed table where I store serialized java objects. They are in the table for 2-3 hours (also are being updated during that period) and then removed. Size of table is around ...
1
vote
1answer
65 views
How to view the current settings of Autovacuum in Postgres?
I've found a million examples of how to set Autovacuum's configuration settings, but can't seem to find how to list the current configuration.
Postgres 9.1 is the version I'm most interested in.
0
votes
2answers
58 views
Slow access to table in postgresql despite vacuum
I'm running PG 8.4
I had a table with about 20K records. Any query accessing this table with more than 1 record (e.g. joins) would be very very slow. Even a count would take like 20 seconds.
Stats ...
1
vote
3answers
163 views
Should I manually VACUUM my PostgreSQL database if autovacuum is turned on?
I use software which makes a big PostgreSQL database (there is a table with a million rows in it) and the developers says I should VACUUM and ANALYZE periodically. But the PostgreSQL database default ...
1
vote
1answer
73 views
Postgres not vacuuming 1 table
I have created a table where I store serialized Java objects. They are frequently accessed and costly to create, so that is the reason. Solution works fine to me, however table size grows to 25GB ...
1
vote
1answer
323 views
Is PostgreSQL 9.2 autovacuum sufficient for a busy table?
I have one table on a PostgreSQL 9.2/PostGIS 2.0.1 database:
CREATE TABLE ch02.markers
(
ff_id SERIAL PRIMARY KEY,
col1 boolean,
col2 smallint,
created_at timestamp,
lat double precision,
...
5
votes
4answers
3k views
Aggressive Autovacuum on PostgreSQL
I'm trying to get PostgreSQL to aggressively auto vacuum my database. I've currently configured auto vacuum as follows:
autovacuum_vacuum_cost_delay = 0 #Turn off cost based vacuum
...
0
votes
1answer
198 views
PostgreSQL vacuum duration on a big table
I have a very big table in my postgreSQL (over 300 million rows) that has never been vacuumed. Yesterday I tried a vacuum and analyze (not a full one) and it took about 7 hours to complete. Will it ...
8
votes
2answers
2k views
Are regular VACUUM ANALYZE stil recommended under 9.1?
I'm using PostgreSQL 9.1 on Ubuntu. Are scheduled VACUUM ANALYZE still recommended, or is autovacuum enough to take care of all needs?
If the answer is "it depends", then:
I have a largish database ...
1
vote
1answer
112 views
How to know there is a maintenance job running on a postgresql database
I have a python script on postgresql database which is fetching records from sql server database and inserting it to postgresql DB after some filtering. this jobs is running by cron every two minutes. ...
2
votes
1answer
802 views
I need to run VACUUM FULL with no available disk space
I have one table that is taking up close to 90% of hd space on our server. I have decided to drop a few columns to free up space. But I need to return the space to the OS. The problem, though, is ...
2
votes
1answer
313 views
Dropping indexes doesn't seem to release space to the OS. Can it?
I'm running PostgreSQL 9.1. I have noticed really alarmingly bad indexes are taking up a lot of space on my server, e.g:
evlampts=# SELECT
pg_size_pretty(pg_relation_size('mcdata_2011_07')) AS ...
2
votes
2answers
158 views
pg_relation_size does not show any difference after VACUUM ANALYZE
I wrote a script to backup a postgresql using COPY and then delete those records. I have used pg_relation_size before and after delete.
pg_relation_size
DELETE
VACUUM ANALYZE
pg_relation_size
But ...
8
votes
1answer
252 views
Disk file effects of delete and vacuum
I have a very frequently updated table with 240 million rows (and growing). Every three hours 1.5 million rows are inserted and 1.5 million are deleted. When I moved the cluster to a SSD this bulk ...
3
votes
2answers
342 views
PostgreSQL unexplained table bloat
I have a table in a Postgres 8.2.15 database. The table bloated to almost 25GB but after running vacuum full and cluster the table size was dramatically smaller, well under 1GB. A few weeks later ...
