Re: Vacuum now uses AccessShareLock for analyze

From: Daniel Kalchev <daniel(at)digsys(dot)bg>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Vacuum now uses AccessShareLock for analyze
Date: 2000-05-29 17:39:57
Message-ID: 200005291739.UAA04615@dcave.digsys.bg
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: 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

Browse pgsql-hackers by date

  From Date Subject
Next Message Bruce Momjian 2000-05-29 17:52:07 Re: Re: Additional system indexes
Previous Message Tom Lane 2000-05-29 17:23:49 Re: pg_* files are too large for empty database.