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 28592.976468370@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:
> There's no command other than VACUUM which continues to
> access table/index after *commit*. We couldn't process
> significant procedures in such an already commiitted state,
> could we ? 

Why not?  The intermediate state *is valid*.  We just haven't
removed no-longer-referenced index and TOAST entries yet.

> What's wrong with vacuuming master and the toast table in
> separate transactions ?

You'd have to give up the lock on the master table if there were
a true commit.  I don't want to do that ... especially not when
I don't believe there is a problem to fix.
        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: Peter Eisentraut
Date:
Subject: Re: F_SETLK is looking worse and worse...