Request a Demo
Home   >   mailing lists

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 CAGRkXqQmg=wOT_4zK7cu9b34Wp_hcG5TD_WeD4mrVGLQ1Ld-1w@mail.gmail.com
Whole thread
In response to Re: REPACK (CONCURRENTLY) decoding worker is canceled by lock_timeout  (shihao zhong <zhong950419@gmail.com>)
Responses Re: REPACK (CONCURRENTLY) decoding worker is canceled by lock_timeout
List pgsql-hackers
Tree view
Hi Alvaro,

I looked at the other settings to see if any of them has the same
problem. I found temp_file_limit, the worker uses it for its decoding
files. 003 fixes it the same way as the timeouts. 

Thanks,
Shihao

Attachment

pgsql-hackers by date:

Previous
From: Richard Guo
Date:
Subject: Unprocessed SubLink from whole-row join alias expansion
Next
From: shihao zhong
Date:
Subject: Re: Report index currently being vacuumed in pg_stat_progress_vacuum