Re: pg_upgrade_replica: avoid full re-clone of standbys after pg_upgrade

From: Greg Sabino Mullane <htamfids(at)gmail(dot)com>
To: Florin Irion <irionr(at)gmail(dot)com>
Cc: Marco Nenciarini <marco(dot)nenciarini(at)enterprisedb(dot)com>, pgsql-hackers(at)postgresql(dot)org, "johncnaylorls(at)gmail(dot)com" <johncnaylorls(at)gmail(dot)com>, "hlinnaka(at)iki(dot)fi" <hlinnaka(at)iki(dot)fi>, "bohyun(dot)lee(at)databricks(dot)com" <bohyun(dot)lee(at)databricks(dot)com>
Subject: Re: pg_upgrade_replica: avoid full re-clone of standbys after pg_upgrade
Date: 2026-09-07 17:59:24
Message-ID: CAKAnmmLSGSdA=UyTNLMb8u9OLq-qcRmDqC-xt7TK_PWBDHSaGQ@mail.gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Mon, Sep 7, 2026 at 11:55 AM Florin Irion <irionr(at)gmail(dot)com> wrote:

> Hello,
>
> I have reviewed the pg_upgrade_replica implementation, and I couldn't
> spot any issue.
>

Did you review it though? And found no issues at all? Because this looks
like an LLM-generated response. It's all generic positive stuff, organized
into small paragraphs. No actual technical review. No "but what about..."
or "on line such and such, why did you...". It provides no value to this
list. Also not clear why you cc'd other people - it's usually polite to
spell out why you did so.

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2026-09-07 18:20:14 Re: Assert failure in try_nestloop_path()
Previous Message Andrew Dunstan 2026-09-07 17:58:57 Re: Concurrent DROP TABLESPACE can miss a shared dependency