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

> -----Original Message-----
> From: Tom Lane [mailto:tgl(at)sss(dot)pgh(dot)pa(dot)us]
>
> "Hiroshi Inoue" <Inoue(at)tpf(dot)co(dot)jp> writes:
> >> Special handling of TOAST relations during VACUUM. TOAST relations
> >> are vacuumed while the lock on the master table is still active.
>
> > It seems very dangerous to me.
> > When VACUUM of a master table was finished, the transaction is
> > in already committed state in many cases.
>
> I don't see the problem. If the toast table doesn't get vacuumed,
> no real harm is done other than failing to recover space.
>

Hmm,is there any good reason to vacuum toast table in the
transaction which was already internally committed by vacuum
of the master table ? Is it possible under WAL ?

Regards.
Hiroshi Inoue