Tom Lane wrote:
>
> "brianb" <brianb-pggeneral@evoserve.com> writes:
> > I have a Postgres application that must run 24x7. If postgres needs to be
> > vacuumed periodically, must I take the application offline completely, or
> > is it enough to disallow write (INSERT/UPDATE) access while allowing read
> > access?
>
> The short answer is that a table being vacuumed is locked against any
> other access, read or write; but only that one table. You might as
> well leave the rest of the database open for use.
I take it you don't give much credence to the previous reports that
concurrently writing during vacuuming caused corruption? Was that a
previous problem that's fixed now?
Regards,
Ed Loehr