Re: [HACKERS] 6.6 items - Mailing list pgsql-hackers

From Vadim Mikheev
Subject Re: [HACKERS] 6.6 items
Date
Msg-id 375CC9F6.3D97B7E0@krs.ru
Whole thread Raw
In response to Re: [HACKERS] 6.6 items  (ZEUGSWETTER Andreas IZ5 <Andreas.Zeugswetter@telecom.at>)
Responses Re: [HACKERS] 6.6 items
List pgsql-hackers
ZEUGSWETTER Andreas IZ5 wrote:
> 
> > - Up time. This means hot backup and no locking of the database during
> > vacuum.
> >
> If Vadim made the change to make pg_dump dump in one transaction then
> PostgreSQL already has "hot backup" in 6.5. This will do a consistent
> snapshot of your database as it was when pg_dump began as long as you
> don't change the database layout during the dump.

This is done.

Vacuum doesn't lock entire database. But it acquires access 
exclusive lock over table being vacuumed and so delay all 
(even SELECT) concurrent query executions. Lock released
after table vacuumed.

Vadim


pgsql-hackers by date:

Previous
From: Dmitry Samersoff
Date:
Subject: Re: [HACKERS] Priorities for 6.6
Next
From: Oleg Broytmann
Date:
Subject: Re: [HACKERS] PostgreSQL History(Parody)