Re: [COMMITTERS] pgsql/src/backend/commands (command.c vacuum.c)

Поиск
Список
Период
Сортировка
От Tom Lane
Тема Re: [COMMITTERS] pgsql/src/backend/commands (command.c vacuum.c)
Дата
Msg-id 1870.976493315@sss.pgh.pa.us
обсуждение исходный текст
Ответ на Re: [COMMITTERS] pgsql/src/backend/commands (command.c vacuum.c)  (Hiroshi Inoue <Inoue@tpf.co.jp>)
Список pgsql-hackers
Hiroshi Inoue <Inoue@tpf.co.jp> writes:
> Tom Lane wrote:
>> Why not?  The intermediate state *is valid*.  We just haven't
>> removed no-longer-referenced index and TOAST entries yet.

> Do you mean *already committed* state has no problem and  
> VACUUM is always possible in the state ?

Yes.  Otherwise VACUUM wouldn't be crash-safe.

> Hmmm,is keeping the lock on master table more important than
> risking to break consistency ?

I see no consistency risk here.  I'd be more worried about potential
risks from dropping the lock too soon.
        regards, tom lane


В списке pgsql-hackers по дате отправления:

Предыдущее
От: Hiroshi Inoue
Дата:
Сообщение: Re: [COMMITTERS] pgsql/src/backend/commands (command.c vacuum.c)
Следующее
От: ncm@zembu.com (Nathan Myers)
Дата:
Сообщение: Re: Re: COPY BINARY file format proposal