| From: | Masahiko Sawada <sawada(dot)mshk(at)gmail(dot)com> |
|---|---|
| To: | Sami Imseih <samimseih(dot)pg(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-30 21:57:05 |
| Message-ID: | CAD21AoA7+O_-z=eF-9jMiZbCJyMTx6MW3jvLTbYGW1BU5EnTdQ@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Wed, Oct 28, 2026 at 3:13 PM Sami Imseih <samimseih(dot)pg(at)gmail(dot)com> wrote:
>
> > 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
Thank you for updating the patch! It looks good to me, so I'll push it
early next week, barring objections.
Regards,
--
Masahiko Sawada
Amazon Web Services: https://aws.amazon.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Masahiko Sawada | 2026-10-30 22:34:14 | Re: Add a hook for handling logical decoding messages on subscribers. |
| Previous Message | Masahiko Sawada | 2026-10-30 21:56:14 | Re: Fix "unexpected logical decoding status change" error; from concurrent logical decoding activation |