Re: REPACK (CONCURRENTLY) decoding worker is canceled by lock_timeout - Mailing list pgsql-hackers

From shihao zhong
Subject Re: REPACK (CONCURRENTLY) decoding worker is canceled by lock_timeout
Date
Msg-id CAGRkXqTsaz9TaioKV0ghofSkAA_sEzKTnxtufRNkuTWbKSCAug@mail.gmail.com
Whole thread
In response to Re: REPACK (CONCURRENTLY) decoding worker is canceled by lock_timeout  (shihao zhong <zhong950419@gmail.com>)
List pgsql-hackers
Hi Alvaro,

A gentle ping on 003. I should have shown the symptom last time. If the
table owner has a role level temp_file_limit, REPACK (CONCURRENTLY) fails
under concurrent updates, even when a superuser runs it:

ERROR:  temporary file size exceeds "temp_file_limit" (64kB)
CONTEXT:  slot "pg_repack_11897", output plugin "pgrepack", in the change callback, associated LSN 0/20A7BF00

That was ALTER ROLE owner SET temp_file_limit = '64kB' and 20k updates
during the REPACK. The caller can't override it, same as the timeouts
before a62ff0829d6. The patch still applies cleanly on master. 

Should we also add that to the open item list?

Thanks,
Shihao

pgsql-hackers by date:

Previous
From: Manu
Date:
Subject: Re: index prefetching
Next
From: Manu
Date:
Subject: Re: REPACK (CONCURRENTLY) can silently lose updates when the toast table is rewritten