Re: "ERROR: could not read block 6 ...: read only 0 of 8192 bytes" after autovacuum cancelled - Mailing list pgsql-hackers

From Pavel Stehule
Subject Re: "ERROR: could not read block 6 ...: read only 0 of 8192 bytes" after autovacuum cancelled
Date
Msg-id 162867790911101104r28b3b264n2a7129e0da52ba1d@mail.gmail.com
Whole thread Raw
In response to Re: "ERROR: could not read block 6 ...: read only 0 of 8192 bytes" after autovacuum cancelled  (Alvaro Herrera <alvherre@commandprompt.com>)
Responses Re: "ERROR: could not read block 6 ...: read only 0 of 8192 bytes" after autovacuum cancelled
List pgsql-hackers
2009/11/10 Alvaro Herrera <alvherre@commandprompt.com>:
> Tom Lane wrote:
>> Alvaro Herrera <alvherre@commandprompt.com> writes:
>> >> 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?
>>
>> Yeah, I would think the problems can manifest all the way back.
>
> Done, thanks for the discussion.

Hello

do you have a idea abou lazy vacuum lockinkg problem?

any plans?

Regards
Pavel Stehule

>
> --
> Alvaro Herrera                                http://www.CommandPrompt.com/
> PostgreSQL Replication, Consulting, Custom Development, 24x7 support
>
> --
> Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
> To make changes to your subscription:
> http://www.postgresql.org/mailpref/pgsql-hackers
>


pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: drop tablespace error: invalid argument
Next
From: Alvaro Herrera
Date:
Subject: Re: "ERROR: could not read block 6 ...: read only 0 of 8192 bytes" after autovacuum cancelled