REPACK (CONCURRENTLY) doesn't check the table AM

From: Nathan Bossart <nathandbossart(at)gmail(dot)com>
To: pgsql-hackers(at)postgresql(dot)org
Cc: alvherre(at)kurilemu(dot)de
Subject: REPACK (CONCURRENTLY) doesn't check the table AM
Date: 2026-08-27 16:23:39
Message-ID: apBkixO4xAGFoiT3@nathan
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

REPACK (CONCURRENTLY) replays changes by decoding them from WAL, so it
needs the table AM to be logically decodable, but
check_concurrent_repack_requirements() doesn't check that. Should it be
restricted to heap for v19?

--
nathan

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Bharath Rupireddy 2026-08-27 16:41:49 REPACK (CONCURRENTLY) backend waits indefinitely when decoding worker fails to start
Previous Message Fujii Masao 2026-08-27 16:20:13 Re: Walreceiver create temp slot more than once when timeline switch