Re: REPACK (CONCURRENTLY) decoding worker is canceled by lock_timeout

From: shihao zhong <zhong950419(at)gmail(dot)com>
To: Álvaro Herrera <alvherre(at)kurilemu(dot)de>
Cc: Chao Li <li(dot)evan(dot)chao(at)gmail(dot)com>, pgsql-hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: REPACK (CONCURRENTLY) decoding worker is canceled by lock_timeout
Date: 2026-09-18 00:52:39
Message-ID: CAGRkXqQmg=wOT_4zK7cu9b34Wp_hcG5TD_WeD4mrVGLQ1Ld-1w@mail.gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

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 Content-Type Size
0003-Have-the-REPACK-decoding-worker-use-temp_file_lim.patch application/octet-stream 3.1 KB

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message shihao zhong 2026-09-18 01:00:08 Re: Report index currently being vacuumed in pg_stat_progress_vacuum
Previous Message Richard Guo 2026-09-18 00:51:37 Unprocessed SubLink from whole-row join alias expansion