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

From Tom Lane
Subject Re: [COMMITTERS] pgsql/src/backend/commands (command.c vacuum.c)
Date
Msg-id 1870.976493315@sss.pgh.pa.us
Whole thread Raw
In response to Re: [COMMITTERS] pgsql/src/backend/commands (command.c vacuum.c)  (Hiroshi Inoue <Inoue@tpf.co.jp>)
List 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 by date:

Previous
From: Hiroshi Inoue
Date:
Subject: Re: [COMMITTERS] pgsql/src/backend/commands (command.c vacuum.c)
Next
From: ncm@zembu.com (Nathan Myers)
Date:
Subject: Re: Re: COPY BINARY file format proposal