Re: "ERROR: could not read block 6 ...: read only 0 of 8192 bytes" after autovacuum cancelled

From: Alvaro Herrera <alvherre(at)commandprompt(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Pg Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: "ERROR: could not read block 6 ...: read only 0 of 8192 bytes" after autovacuum cancelled
Date: 2009-11-07 00:18:37
Message-ID: 20091107001837.GK3840@alvh.no-ip.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Tom Lane wrote:
> Alvaro Herrera <alvherre(at)commandprompt(dot)com> writes:
> > Tom Lane wrote:
> >> I wonder whether we shouldn't extend this into VACUUM FULL too, to
> >> prevent cancel once it's done that internal commit. It would fix
> >> the "PANIC: can't abort a committed transaction" problem V.F. has.
>
> > Hmm, it seems to work. The attached is for 8.1.
>
> Looks OK, but please update the comment right before the
> RecordTransactionCommit, along the lines of "We prevent cancel
> interrupts after this point to mitigate the problem that you
> can't abort the transaction now".

BTW I'm thinking in backpatching this all the way back to 7.4 -- are
we agreed on that?

--
Alvaro Herrera http://www.CommandPrompt.com/
The PostgreSQL Company - Command Prompt, Inc.

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2009-11-07 00:54:23 Re: "ERROR: could not read block 6 ...: read only 0 of 8192 bytes" after autovacuum cancelled
Previous Message Tom Lane 2009-11-07 00:05:13 Re: operator exclusion constraints