Re: Adding REPACK [concurrently]
От | Fujii Masao |
---|---|
Тема | Re: Adding REPACK [concurrently] |
Дата | |
Msg-id | CAHGQGwHCeqXUoNaJuftWjOkB8_LSmyH7Md9qkR79sOtW9DJe2Q@mail.gmail.com обсуждение исходный текст |
Ответ на | Re: Adding REPACK [concurrently] (Alvaro Herrera <alvherre@alvh.no-ip.org>) |
Список | pgsql-hackers |
On Fri, Aug 1, 2025 at 1:50 AM Alvaro Herrera <alvherre@alvh.no-ip.org> wrote: > One of the later patches in the series, which I have not included yet, > intends to implement the idea of transiently enabling wal_level=logical > for the table being repacked concurrently, so that you can still use > the concurrent mode if you have a non-logical-wal_level instance. Sounds good to me! > Here's v17. I just tried REPACK command and observed a few things: When I repeatedly ran REPACK on the regression database while make installcheck was running, I got the following error: ERROR: StartTransactionCommand: unexpected state STARTED "REPACK (VERBOSE);" failed with the following error. ERROR: syntax error at or near ";" REPACK (CONCURRENTLY) USING INDEX failed with the following error, while the same command without CONCURRENTLY completed successfully: =# REPACK (CONCURRENTLY) parallel_vacuum_table using index regular_sized_index ; ERROR: cannot process relation "parallel_vacuum_table" HINT: Relation "parallel_vacuum_table" has no identity index. When I ran REPACK (CONCURRENTLY) on a table that's also a logical replication target, I saw the following log messages. Is this expected? =# REPACK (CONCURRENTLY) t; LOG: logical decoding found consistent point at 1/00021F20 DETAIL: There are no running transactions. STATEMENT: REPACK (CONCURRENTLY) t; Regards, -- Fujii Masao
В списке pgsql-hackers по дате отправления: