Thread

BUG #14852: Refreshing materialized view might lead to a problem "could not access status of transaction"

Alexey Ermakov <alexey.ermakov@dataegret.com> — 2017-10-13T11:53:20Z

The following bug has been logged on the website:

Bug reference:      14852
Logged by:          Alexey Ermakov
Email address:      alexey.ermakov@dataegret.com
PostgreSQL version: 9.6.5
Operating system:   Ubuntu 16.04.3 LTS, CentOS 7.3.1611
Description:        

Hello,

I found strange error messages in logs:

2017-10-01 04:53:54 MSK 16183 @ from  [vxid:48/16835960 txid:0] [] ERROR: 
could not access status of transaction 657045744
2017-10-01 04:53:54 MSK 16183 @ from  [vxid:48/16835960 txid:0] [] DETAIL: 
Could not open file "pg_clog/0272": No such file or directory.
2017-10-01 04:53:54 MSK 16183 @ from  [vxid:48/16835960 txid:0] [] CONTEXT: 
automatic vacuum of table "dbname.pg_toast.pg_toast_605700155

toast table belongs to materialized view. Errors started to appear right
after function which refreshes materialized views concurrently was called.

What is more strange that this problem happened on two completely different
projects/servers recently. Both times "could not access status of
transaction" and materialized views.
I suspect it might be some new bug since both DBs were recently upgraded
from 9.4 to 9.6.4/9.6.5 and I haven't seen that before.