Re: Making pg_rewind faster

From: Michael Paquier <michael(at)paquier(dot)xyz>
To: Robert Haas <robertmhaas(at)gmail(dot)com>
Cc: John H <johnhyvr(at)gmail(dot)com>, wenhui qiu <qiuwenhuifx(at)gmail(dot)com>, Japin Li <japinli(at)hotmail(dot)com>, Andres Freund <andres(at)anarazel(dot)de>, Alexander Korotkov <aekorotkov(at)gmail(dot)com>, Justin Kwan <justinpkwan(at)outlook(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>, vignesh <vignesh(at)cloudflare(dot)com>, vignesh ravichandran <admin(at)viggy28(dot)dev>, "hlinnaka(at)iki(dot)fi" <hlinnaka(at)iki(dot)fi>, "jkwan(at)cloudflare(dot)com" <jkwan(at)cloudflare(dot)com>
Subject: Re: Making pg_rewind faster
Date: 2025-10-23 05:12:24
Message-ID: aPm5OFDGocOSSwfb@paquier.xyz
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Thu, Sep 25, 2025 at 02:35:16PM -0400, Robert Haas wrote:
> On a related note, something a committer would need to do if they
> wanted to commit this patch is figure out who should be credited with
> writing it. I see that a number of different people have posted
> versions of the patch; it would be nice if "Author:" or
> "Co-authored-by:" tags were added to the commit message to reflect
> whose code is present in a given version.

Looking at this patch was on my TODO list (more to that in a bit), and
the simplest answer to this question is that everybody involved would
be cited in the release notes. Justin Kwan has been the original
author. John Hsu and Srinath have followed up in an equivalent
fashion, including answers with your review comments posted on this
previous message. So listing all three as equivalent authors feels
normal to me (no need for co-authoring notes, IMO).
--
Michael

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message vignesh C 2025-10-23 06:15:17 Re: Logical Replication of sequences
Previous Message Amit Kapila 2025-10-23 04:48:37 Re: POC: enable logical decoding when wal_level = 'replica' without a server restart