Bug 159650 – database not vacuumed by default

Bug 159650 - database not vacuumed by default

Summary:	database not vacuumed by default

Status:	CLOSED DEFERRED

Aliases:	None

Product:	Fedora
Classification:	Fedora
Component:	postgresql (Show other bugs)
Sub Component:
Version:	rawhide
Hardware:	All Linux

Priority	medium Severity medium
Target Milestone:	---
Target Release:	---
Assigned To:	Tom Lane
QA Contact:	David Lawrence
Docs Contact:

URL:
Whiteboard:
Keywords:

Depends On:
Blocks:
	Show dependency tree / graph

Reported:	2005-06-06 11:48 EDT by Rik van Riel
Modified:	2013-07-02 23:06 EDT (History)
CC List:	1 user (show)

See Also:
Fixed In Version:
Doc Type:	Bug Fix
Doc Text:
Story Points:	---
Clone Of:
Environment:
Last Closed:	2005-09-30 15:03:50 EDT
Type:	---
Regression:	---
Mount Type:	---
Documentation:	---
CRM:
Verified Versions:
Category:	---
oVirt Team:	---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---

Attachments	(Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

Groups: None (edit)

Description Rik van Riel 2005-06-06 11:48:44 EDT

Description of problem:

The postgresql install in Fedora and RHEL does not start database vacuuming of
any kind.  IMHO it would be a good idea to have pg_autovacuum running by
default, configured to analyse and vacuum the tables after reasonable intervals.
  
Reclaiming disk space is the one area I can think of where mysql is currently
better than postgres, it would be nice to close the gap here ;)

Comment 1 Tom Lane 2005-09-30 15:03:50 EDT

I think this would probably be reasonable to do in PG 8.1, where autovacuum is
built into the core database.  I don't have enough confidence in the external
contrib version of autovacuum to want to turn it on by default.

Note You need to log in before you can comment on or make changes to this bug.