Re: Vacuum now uses AccessShareLock for analyze - Mailing list pgsql-hackers

From Daniel Kalchev
Subject Re: Vacuum now uses AccessShareLock for analyze
Date
Msg-id 200005291739.UAA04615@dcave.digsys.bg
Whole thread Raw
In response to Re: Vacuum now uses AccessShareLock for analyze  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
While we are at VACUUM, it would be good idea to have VACUUM flag each 'vacuumed' table (with some sort of 'clean'
flag)- this will permit vaster vacuuming of mostly static databases, such that contain 'history' data in some tables.
 

Daniel



pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: pg_* files are too large for empty database.
Next
From: Bruce Momjian
Date:
Subject: Re: Re: Additional system indexes