| From: | Sami Imseih <samimseih(dot)pg(at)gmail(dot)com> |
|---|---|
| To: | Masahiko Sawada <sawada(dot)mshk(at)gmail(dot)com> |
| Cc: | Postgres hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: Add REPACK progress phases for logical decoding setup |
| Date: | 2026-10-28 22:12:58 |
| Message-ID: | CAN12+YJyT_rTkuUL2wyK55ZCwN9nOYxdBRtpUZ=gTdMvqiW33g@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
> I've reviewed the patch and it mostly looks good to me. I have one
> minor comment:
>
> /* Find our decoding starting point. */
> + set_repack_worker_setup_phase(shared,
> + PROGRESS_REPACK_PHASE_INIT_LOGICAL_DECODING);
> DecodingContextFindStartpoint(ctx);
>
> While it's true that DecodingContextFindStartpoint() is the call that
> can take a long time in this phase, I'd recommend setting the
> INIT_LOGICAL_DECODING phase just before calling
> CreateInitDecodingContext(). Otherwise, if CreateInitDecodingContext()
> takes time for some reason, it would be reported as "enabling logical
> decoding", which the documentation describes as having nothing to do
> when effective_wal_level is already logical.
Makes sense. Done in v5
--
Sami Imseih
Amazon Web Services (AWS)
| Attachment | Content-Type | Size |
|---|---|---|
| v5-0001-Add-REPACK-progress-phases-for-logical-decoding-s.patch | application/octet-stream | 11.6 KB |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Thomas Munro | 2026-10-28 22:18:57 | Re: Skip prefetch for block references that follow a FPW or WILL_INIT of the same block |
| Previous Message | Masahiko Sawada | 2026-10-28 21:48:45 | Re: Add REPACK progress phases for logical decoding setup |