Re: [cstdenis@ctgameinfo.com: Re: BUG #3179: crash when canceling avacuum]

Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org> writes:
> ----- Forwarded message from Cstdenis <cstdenis(at)ctgameinfo(dot)com> -----
> Mar 20 22:29:48 ayu postgres[60274]: [1-1] ERROR: canceling statement due
> to user request
> Mar 20 22:29:48 ayu postgres[60274]: [1-2] STATEMENT: VACUUM FULL VERBOSE
> ANALYZE;
> Mar 20 22:29:48 ayu postgres[60274]: [2-1] PANIC: cannot abort
> transaction 293233494, it was already committed

Oh, this is a well-known problem: VACUUM FULL plays a game it shouldn't
be playing with marking its transaction committed before it's really done.

I think we now have enough infrastructure to clean this up by turning
a VACUUM FULL into two successive transactions, but haven't got round to
looking at it in detail.

regards, tom lane