RE: Memory leak fix in psql - Mailing list pgsql-hackers

From tanghy.fnst@fujitsu.com
Subject RE: Memory leak fix in psql
Date
Msg-id OS0PR01MB611337599CCEF8A9076D9ACDFB8E9@OS0PR01MB6113.jpnprd01.prod.outlook.com
Whole thread Raw
In response to Re: Memory leak fix in psql  (Junwang Zhao <zhjwpku@gmail.com>)
Responses Re: Memory leak fix in psql
List pgsql-hackers
> On Wed, Jul 20, 2022 at 12:51:24PM +0800, Junwang Zhao wrote:
> > Though the patch looks good, I myself think the patch should be edited
> > and submitted by Tang
> > It's easy to attach a fixed patch based on the comments of the thread,
> > but coins should be
> > given to Tang since he is the first one to find the mem leak.

Hello, Zhao

Thanks for your check at this patch. 

I appreciate your kindly comment but there may be a misunderstanding here.
As Michael explained, committers in Postgres will review carefully and 
help to improve contributors' patches. When the patch is finally committed 
by one committer, from what I can see, he or she will try to make sure the 
credit goes with everyone who contributed to the committed patch(such as 
bug reporter, patch author, tester, reviewer etc.). 

Also, developers and reviewers will try to help improving our proposed patch
by rebasing it or adding an on-top patch(like Japin Li did in v2).
These will make the patch better and to be committed ASAP.

Good to see you at Postgres community.

Regards,
Tang

pgsql-hackers by date:

Previous
From: tushar
Date:
Subject: Re: replacing role-level NOINHERIT with a grant-level option
Next
From: Marco Slot
Date:
Subject: Re: [PATCH] Use indexes on the subscriber when REPLICA IDENTITY is full on the publisher