Re: [HACKERS] 6.6 items

Поиск
Список
Период
Сортировка
От Vadim Mikheev
Тема Re: [HACKERS] 6.6 items
Дата
Msg-id 375CC9F6.3D97B7E0@krs.ru
обсуждение исходный текст
Ответ на Re: [HACKERS] 6.6 items  (ZEUGSWETTER Andreas IZ5 <Andreas.Zeugswetter@telecom.at>)
Ответы Re: [HACKERS] 6.6 items  (Don Baccus <dhogaza@pacifier.com>)
Список 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 по дате отправления:

Предыдущее
От: Dmitry Samersoff
Дата:
Сообщение: Re: [HACKERS] Priorities for 6.6
Следующее
От: Oleg Broytmann
Дата:
Сообщение: Re: [HACKERS] PostgreSQL History(Parody)